Skip to main content
Glama

Are my replies on track?

reply_pace
Read-onlyIdempotent

Weekly pace check for one market: pass the buyers emailed so far (each buyer once, first emails only), the buyers who replied (any reply, a no counts) and, if known, the week of the 13-week schedule and how many replies were interested (warm). Call it first in the weekly routine and act on it before anything else: relay risk_note first when present (sanctions or export controls on that market), then status_text, advice (or decision_text once the target is reached) and send_this_week as they are; find_buyers_type is this week's buyer type and email_draft the first email to use (first_email or a key of gtm_plan first_email_variants); changed lists the changes made so far, to pass back next week; they agree with each other and with the web plan, and each gives one change to make, not a choice. Returns: status (one of too_early, no_replies, below, change_now, decision_moves, behind_schedule, normal_range, few_interested, above, on_track, or the decision next_market, change_and_retry, keep_going; on_track only when the current rate reaches 10 replies at the target, sends are on schedule and the interested share is not low), status_text, advice, send_this_week (new buyers to add this week: the catch-up number when more than a week behind; at next_market the first 200 in send_this_week_in), the rate Korean exporters of this product usually get there (the same industry × market rate as gtm_plan reply_target, from 2.2M real export emails), the normal range for that many sends (Poisson 5–95%), projected_replies_at_target, alternative_buyer_type, behind_schedule (weeks 2–12), decision_moves (week 13 or later before the target: the week to decide), and from 95% of sends_for_10_replies the decision with decision_text (fewer than 5 replies → next_market, named only then; 5–9 → same market once more, the next buyer type with a new subject line for retry_batch.send more, then 10 or more in total keeps going and fewer moves on; 10 or more → keep going). Pass exclude with markets already tried. With warm it adds warm_share against the usual share; when low (from 5 replies, under half the usual share) the status or decision says to change the offer and warm_note explains. Reply rates measure emails sent through RINDA, so a low count can be a sending problem rather than the market: with opened or bounced it adds reach_check, and when opens fall below the share people open in TradeGraph's data or bounces exceed 10% while replies look weak, decision fix_reach_first holds the market decision until sending is fixed (decision_by_replies keeps the replies-only decision). With samples, quotes, meetings or orders it adds pipeline: an order keeps the market (keep_going) and 2 or more meetings or 3 or more sample and quote requests turn next_market into one more retry. last_sent and last_replies catch weekly numbers passed instead of running totals. Called signed in (/mcp/account) for a market with a saved buyer list, it adds account_note (the list's size, list_unsent — how many on it are not emailed yet by the sent number passed, counted from the front of the list — and the buyer types whose map searches have all run) and points to my_progress, which plans the week with that list. Free, read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "item": "<item>",
      "country": "<country>",
      "sent": "<sent>",
      "replies": "<replies>"
    },
    "name": "reply_pace"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYesProduct as an HS4 code (e.g. '3304') or a name in English or Korean (e.g. 'sunscreen', '라면'). Names cover TradeGraph's 35 items; any other product works as a 4-digit HS code (e.g. '1905' biscuits, '2005' kimchi, '3305' shampoo) with live UN Comtrade imports.
sentYesBuyers emailed so far in this market (count each buyer once; follow-ups don't add).
warmNoOptional: of the replies, how many were interested (a question, a sample request or a meeting; not a no). Compared with the usual interested share of replies; from 5 replies a low share adds warm_note.
weekNoOptional: the week of the 13-week schedule they are in (1 = the week of the first 200 emails), to flag sends behind schedule or a decision that moves past week 13.
openedNoOptional: of the buyers emailed, how many opened at least one email, as the user's email tool reports it (unique opens). Below the share of delivered emails people open in TradeGraph's data, the emails are probably not reaching inboxes: reach_check says so and holds a market switch (decision fix_reach_first).
ordersNoOptional: buyers who placed an order (trial orders count). An order keeps the market even with few replies (pipeline).
quotesNoOptional: buyers who asked for prices or a quote.
bouncedNoOptional: buyers whose email bounced. Over 10% of sent holds a market switch until the list is verified (reach_check list_problem).
changedNoOptional: changes already made in earlier weeks, as last week's changed (comma-separated: next_type, new_subject, new_subject_2, offer, retry, retry_type). A change once made is kept: the same verdict again keeps it instead of flipping back, a retry uses a subject line not sent yet, and retry (a retry batch already started) keeps that subject line in the following weeks; retry_type (the retry switched to a buyer type not tried yet) keeps that type's email. my_progress does this from the saved log.
countryYesTarget country as ISO 3166-1 alpha-2 (e.g. 'US', 'JP') or an English/Korean name.
excludeNoOptional: markets already tried, comma-separated ISO codes or names (e.g. 'DE,PL'), skipped when naming the next market.
repliesYesBuyers who replied so far (any reply, including a no).
samplesNoOptional: buyers who asked for samples.
conceptsNoOptional: the same concepts passed to gtm_plan (halal, vegan, derma …).
meetingsNoOptional: buyers who agreed to a meeting or a call.
last_sentNoOptional: last week's sent total, to catch this week's numbers passed instead of running totals (sent lower than last_sent is rejected).
buyer_typeNoOptional: the buyer type the user sent to last week (last week's find_buyers_type); after a switch to the next type the check keeps it.
price_tierNoOptional: the same price tier passed to gtm_plan.
selling_inNoOptional: the same selling_in passed to gtm_plan (markets where the product already sells).
descriptionNoOptional: the same product description passed to gtm_plan, so next_market follows the same ranking (entry_paths).
last_repliesNoOptional: last week's replies total (replies lower than last_replies is rejected).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / concepts
      Added value: +{
      +  "description": "Optional: the same concepts passed to gtm_plan (halal, vegan, derma …).",
      +  "type": "string"
      +}
    • addedInput schema / properties / description
      Added value: +{
      +  "description": "Optional: the same product description passed to gtm_plan, so next_market follows the same ranking (entry_paths).",
      +  "type": "string"
      +}
    • addedInput schema / properties / price_tier
      Added value: +{
      +  "description": "Optional: the same price tier passed to gtm_plan.",
      +  "enum": [
      +    "premium",
      +    "mass"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / selling_in
      Added value: +{
      +  "description": "Optional: the same selling_in passed to gtm_plan (markets where the product already sells).",
      +  "type": "string"
      +}
  2. Changed8 schema fields changed
    • addedInput schema / properties / bounced
      Added value: +{
      +  "description": "Optional: buyers whose email bounced. Over 10% of sent holds a market switch until the list is verified (reach_check list_problem).",
      +  "maximum": 1000000,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / last_replies
      Added value: +{
      +  "description": "Optional: last week's replies total (replies lower than last_replies is rejected).",
      +  "maximum": 1000000,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / last_sent
      Added value: +{
      +  "description": "Optional: last week's sent total, to catch this week's numbers passed instead of running totals (sent lower than last_sent is rejected).",
      +  "maximum": 1000000,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / meetings
      Added value: +{
      +  "description": "Optional: buyers who agreed to a meeting or a call.",
      +  "maximum": 1000000,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / opened
      Added value: +{
      +  "description": "Optional: of the buyers emailed, how many opened at least one email, as the user's email tool reports it (unique opens). Below the share of delivered emails people open in TradeGraph's data, the emails are probably not reaching inboxes: reach_check says so and holds a market switch (decision fix_reach_first).",
      +  "maximum": 1000000,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / orders
      Added value: +{
      +  "description": "Optional: buyers who placed an order (trial orders count). An order keeps the market even with few replies (pipeline).",
      +  "maximum": 1000000,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / quotes
      Added value: +{
      +  "description": "Optional: buyers who asked for prices or a quote.",
      +  "maximum": 1000000,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / samples
      Added value: +{
      +  "description": "Optional: buyers who asked for samples.",
      +  "maximum": 1000000,
      +  "minimum": 0,
      +  "type": "integer"
      +}
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, but the description adds substantial behavior beyond that: status states, decision logic, reach_check and pipeline overrides, account_note behavior, and validation through last_sent and last_replies. It is consistent with the read-only annotation and does not contradict it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and usage are front-loaded, which is good, but the description becomes a dense run-on paragraph with many semicolon-separated clauses. Much of the detail is necessary for this complex tool, yet the lack of bullets or sectioning reduces scannability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the 21 parameters, lack of an output schema, and complex decision logic, the description supplies return statuses, return fields, edge cases, and sibling handoffs. It is complete enough for an agent to invoke the tool and interpret the result correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all 21 parameters are already documented in the input schema. The description still adds meaningful cross-parameter behavior, such as warm triggering warm_share/warm_note, opened or bounced invoking reach_check/fix_reach_first, samples/quotes/meetings/orders affecting the decision, changed carrying prior changes, and exclude determining the next market.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence names a specific verb and resource: 'Weekly pace check for one market'. It also distinguishes the tool from siblings by calling itself the first step in the weekly routine and pointing to my_progress and gtm_plan for related work.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says to call it first in the weekly routine and act on it before anything else, and explains how to use the returned fields. It names my_progress as the saved-list planner and gtm_plan as the source of the target rate, but it does not give a clear when-not-to-use rule or full alternative routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.