@talqing/mcp 0.6.0 → 0.7.0

package/SKILL.md

@@ -1144,8 +1144,16 @@ overrides of anything else — one batch is one agent, one number, one clock.
 weekdays it may dial in, so a list uploaded at 23:00 can start at 11:00
 tomorrow, stop at 18:00 and resume at 10:00 on the next weekday untouched. A
 window may cross midnight; the days then name the evening it starts on.
-`next_dial_at` on the batch says when it will dial next, which is how you tell
-"waiting for Monday" apart from "stuck".
+`next_dial_at` on the batch says when it will dial next and `next_dial_reason`
+why (`start`, `window`, `daily_cap`), which is how you tell "waiting for Monday"
+apart from "stuck".
+
+**Pace.** `dial_gap_seconds` is the minimum wait between starting two calls (0,
+the default, dials as slots free). `dial_daily_cap` limits calls placed per
+local day, retries included: `{kind: "fixed", limit}` or a ramp, `{kind: "ramp",
+start, end, step, interval_days}`, which rises by `step` every `interval_days`
+days the batch actually dialled. For a new caller ID suggest a ramp rather than
+a flat limit. `dialed_today` is measured against `dial_daily_cap_today`.
 
 **Say these two things before creating one**, because a user who discovers
 either from an invoice will not forgive us:
@@ -1242,7 +1250,10 @@ row. `create_email_send` takes a `scope` and returns a **send** you can steer:
 - `start_at` schedules it, `window` (on its own `timezone`) holds it to business
   hours, `send_gap_seconds` is the minimum wait between two emails of the
   **batch** (1 second to 1 hour) and `send_daily_cap` bounds how many the batch
-  may send per local day. Anything omitted comes from the batch.
+  may send per local day: `{kind: "fixed", limit}`, or a ramp, `{kind: "ramp",
+  start, end, step, interval_days}`, which rises by `step` every `interval_days`
+  days the batch actually sent (a weekend or a pause earns nothing). Anything
+  omitted comes from the batch.
 - A draft a live send covers reads `queued`, and is still a draft: it can be
   edited, skipped or redrafted until the send takes it.
 - `pause_email_send` stops on the next email; `resume_email_send` carries on.
@@ -1254,9 +1265,10 @@ row. `create_email_send` takes a `scope` and returns a **send** you can steer:
   within five minutes, so raising a spent cap or removing a window needs no
   cancel.
 
-**The safeguard here is a RATE, not a row count.** `send_daily_cap` (200 by
-default, per batch, `null` for uncapped) is what stands between a 5 000-row list
-and a sending domain nobody trusts again. Before creating a send, say how many
+**The safeguard here is a RATE, not a row count.** `send_daily_cap` (a fixed
+200 by default, per batch, `null` for uncapped) is what stands between a
+5 000-row list and a sending domain nobody trusts again. For a new sending
+domain, suggest a ramp (say 10 rising to 50) rather than a flat cap. Before creating a send, say how many
 emails it is and roughly how long it will take at the pace it has — and if the
 user asks to raise or remove the cap, say what it is for rather than just doing
 it.
@@ -1301,7 +1313,7 @@ ours — Resend keeps one and auto-suppresses hard bounces and complaints.
 
 `get_email_batch` carries live counts, `skips` (why rows were skipped),
 `draft_failures` (why drafts failed, most common first), `failure_reason`,
-`sent_today` (against `send_daily_cap`), `drafted_versions`,
+`sent_today` (against `send_daily_cap_today`), `drafted_versions`,
 `stale_redraftable` / `stale_sent` and the drafting cost so far. Measure
 progress against what can be reached: `unfillable` rows are never drafted, and
 skipped, failed or cancelled rows are never sent.
@@ -1325,7 +1337,9 @@ gives a sender's approved templates — header, body, footer, buttons and variab
 names; one with `unsupported_reason` cannot be used.
 `create_whatsapp_batch` maps `to_column` and every variable onto CSV columns. A
 row with a bad or repeated phone, or a blank mapped cell, is kept and skipped
-with the reason, so read the returned `counts`.
+with the reason, so read the returned `counts`. `send_daily_cap` takes the same
+object an email batch's does (a fixed 250 by default); for a new sender suggest
+a ramp.
 
 **Say these before creating one:**
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@talqing/mcp",
-  "version": "0.6.0",
+  "version": "0.7.0",
   "description": "MCP server for building Talqing AI voice, video and text agents from Claude Code, Codex, or any MCP client.",
   "license": "MIT",
   "homepage": "https://talqing.com",