Skip to main content
Glama

clawbridge_reply

Sends a text reply to a task awaiting ordinary input so remote development workflows can continue. Use only for normal input, not approvals, deployments, or credential access.

Instructions

Reply to a task waiting for ordinary input. Never use this tool to approve permissions, destructive operations, releases, deployments, or credential access.

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": {
      "taskId": "<taskId>",
      "text": "<text>"
    },
    "name": "clawbridge_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
taskIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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. The exclusion list usefully signals that this is a non-privileged, non-destructive channel, but it does not say whether replying resumes/completes the task, whether it is idempotent, what happens if the task is not actually waiting, or what is returned.

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

Conciseness5/5

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

Two sentences, front-loaded with the primary action, then the guardrail. Nothing is padding and nothing is buried.

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?

No output schema and no annotations, so the description should cover the reply's effect and preconditions; it covers only the negative scope. An agent knows when not to call it but not what a successful call changes or returns.

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

Parameters2/5

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

Schema description coverage is 0% on both parameters. The description adds no meaning about taskId (where to obtain it, whether it must be a waiting task) or text (whether it is delivered verbatim, truncated, or interpreted). The schema's UUID pattern and 20k length cap are the only constraints, and they come from the schema, not the description.

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?

States a specific verb and resource (reply to a task) plus a scoping qualifier ('waiting for ordinary input'), which separates it from the permission-answering sibling. It never explains what a 'task' is or where the reply lands, so it stops short of a 5.

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?

Gives an explicit negative rule enumerating six excluded categories (permissions, destructive operations, releases, deployments, credential access), which effectively routes an agent away from this tool toward the approval tool. It does not name the correct alternative, so routing is inferred rather than stated.

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