Skip to main content
Glama

Reply in a business conversation

reply_to_business
DestructiveIdempotent

Answer a business in an existing Direct conversation. Use it after get_replies shows the business answered or asked something; to start a new conversation use send_to_business, and to answer a question during a live phone call use answer_call_question. Pass the thread_id that send_to_business returned and the reply text (1 to 500 characters); sign in as the original requester with direct:tasks, or supply the private thread_token instead. message_id is the retry key: reuse it unchanged when retrying. Returns the A2A {task} for the reply: read its state before telling anyone it was delivered. A delivered reply cannot be recalled and is billed the same way as a take_message task; closed conversations refuse replies. Example: thread_id='th_7c1', text='Thursday after 2pm works, thank you.', message_id='rep-1'.

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": {
      "thread_id": "<thread_id>",
      "text": "<text>"
    },
    "name": "reply_to_business"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe customer’s reply to the business.
thread_idYesThe thread_id returned by send_to_business.
message_idNoYour id for this reply; reuse it unchanged when retrying.
thread_tokenNoThe private thread_token; required unless signed in as the requester who started the thread.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing that a delivered reply cannot be recalled, that replies are billed like a take_message task, that closed conversations refuse replies, and that callers must read the returned task state before claiming delivery. It also explains the auth model (sign in as the original requester with direct:tasks or supply thread_token). It stops short of stating rate limits or the failure modes/signals returned on refusal, but the key irreversible side effects are covered consistent with destructiveHint=true.

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

Conciseness4/5

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

Front-loads the purpose and alternatives, then moves to prerequisites, retry semantics, and return value, ending with a concrete example. It is dense — the third sentence carries several distinct obligations — but nearly every clause adds actionable information rather than restating the name or annotations.

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?

With no output schema, the description still explains the return value (the A2A {task} for the reply) and what to inspect in it. Auth requirements, retry/idempotency, billing, irreversibility, and the closed-conversation failure case are all present, which is complete for a 4-parameter mutating tool.

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 coverage is 100%, so the baseline is 3, but the description adds genuine meaning: thread_id is the value returned by send_to_business, text is bounded 1–500 characters, message_id is the retry key to reuse unchanged, and thread_token is the alternative credential when not signed in as the requester. Only the exact auth scope string is left implicit in the schema, so this exceeds the baseline.

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?

States a specific verb and resource ('Answer a business in an existing Direct conversation') and immediately scopes it against siblings: send_to_business is for starting a new conversation and answer_call_question is for live calls. An agent can distinguish this tool from its nearest alternatives without opening any schema.

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

Usage Guidelines5/5

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

Provides an explicit trigger ('use it after get_replies shows the business answered or asked something') plus two named alternatives with the conditions that select them. The prerequisite that the conversation must already exist and be open is also stated, leaving nothing to inference.

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.

Resources