Skip to main content
Glama

bridge_answer

Send a reply to a shared task through the v2 bridge service. Use it to answer questions or complete reviews between Claude Code and Codex on the same machine.

Instructions

Execute bridge answer through the v2 service.

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>",
      "body": "<body>"
    },
    "name": "bridge_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
no_wakeNo
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

D1.5/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure, and it discloses nothing. It does not say whether this mutates state, whether answers are final or editable, what permissions are required, what no_wake suppresses, or what the call returns.

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

Conciseness2/5

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

It is a single short sentence with no padding, but the brevity reflects under-specification rather than economy. The one clause that exists ("through the v2 service") conveys implementation trivia instead of actionable information.

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

Completeness1/5

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

For a three-parameter tool with zero schema documentation, no annotations, and no output schema, the description supplies none of the missing context. An agent cannot reliably decide when to call it or how to populate its arguments from this definition.

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

Parameters1/5

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

Schema description coverage is 0% across three parameters, and the description mentions none of them. The meaning of task_id, body, and especially no_wake is left entirely unexplained in both structured and unstructured fields.

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

Purpose2/5

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

"Execute bridge answer through the v2 service" essentially restates the tool name (bridge_answer) with a generic verb and a service-version tag. It never says what an "answer" is, what resource it targets, or how it differs from siblings like bridge_question or bridge_send.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no named alternative. The only faint signal is the word "answer," which hints at responding to a pending question, but the agent must infer even that from the name rather than the description.

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