Skip to main content
Glama

bridge_question

Send a question through the v2 bridge service to another agent, referencing a task ID and message body, to exchange clarifications between Claude Code and Codex.

Instructions

Execute bridge question 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_question"
  }
}

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?

With no annotations and no output schema, the description carries the full behavioral burden and delivers none of it. It does not disclose whether this is a write operation, what a question does downstream (does it block, notify, or wake an agent?), what the no_wake flag suppresses, or what errors occur on an invalid task_id.

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?

The single sentence is short but it is short because it omits everything, not because it is efficient. There is no front-loaded purpose statement, no parameter note, and the only substantive phrase ("v2 service") is internal implementation detail of little use to a selecting agent.

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?

This is a three-parameter, two-required action tool with zero annotation coverage, zero schema coverage, and no output schema — the highest possible burden on the description, which meets none of it. An agent cannot confidently select or safely invoke this tool from the definition alone.

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, so the description must compensate and instead says nothing about any of them. The meanings of task_id (which task?), body (question text? JSON payload?), and especially no_wake are left entirely to guesswork.

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 question through the v2 service" restates the tool name with a generic verb and adds only the internal detail that a v2 service exists. It gives no indication of what a "bridge question" actually is (asking a coordinating agent? posting a question to a queue?) and nothing distinguishes it from siblings such as bridge_answer, bridge_send, or bridge_inbox.

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 guidance on when to call this tool, no prerequisites, and no mention of alternatives. The presence of a sibling named bridge_answer makes the missing "use this when you need to ask; use bridge_answer to respond" routing especially costly, but the description supplies none of it.

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