Skip to main content
Glama

reply

Send a response to a received task, message, or file by its inbox task ID; provide a status for task results and omit it for messages or files.

Instructions

Answer a task, message or file you received, by the id inbox showed (task_id): sends text to its sender; status (done, failed, declined or timeout) is required for a task's result and ignored for a message or file.

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": {
      "task_id": "<task_id>",
      "text": "<text>"
    },
    "name": "reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
statusNo
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the meaningful side effect (text is delivered to the original sender) and the conditional status semantics. It omits what happens on invalid/foreign task_id, whether replying finalizes or closes the task, and whether duplicate replies are allowed.

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?

A single dense sentence that front-loads the action and packs the addressing rule and status conditionality with no filler. The phrasing ('by the id inbox showed') is slightly awkward, but nothing is wasted.

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

Completeness3/5

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

For a 3-parameter mutation tool with no annotations and no output schema, the definition covers addressing and status rules but leaves the response undescribed (no output schema exists to cover it) and says nothing about error behavior or task-state effects.

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 0%, so the description must compensate, and it does for two of three parameters: task_id is defined as the id inbox showed, and status is explained as required for task results and ignored otherwise, matching the enum. The 'text' parameter is obvious from its role but never explicitly described.

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

Purpose4/5

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

The description states a specific action (answer a received task, message or file by sending text to its sender) and identifies the resource family and addressing key (task_id as shown in inbox). It is clearly not a broadcast/send-new tool, though it never explicitly distances itself from the sibling 'send'.

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?

It scopes usage to items you received and whose id inbox showed, which implicitly excludes composing new outbound messages. It also gives conditional guidance that status applies to task results and is ignored for messages/files. No explicit alternative (e.g. 'use send for new messages') is named.

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

Deploy Server

Other Tools