Skip to main content
Glama

bridge_send

Send a task, question, review, or reply from Claude Code or Codex to another agent on the same machine, with optional project tagging and wake suppression.

Instructions

Execute bridge send 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": {
      "to": "<to>",
      "subject": "<subject>"
    },
    "name": "bridge_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
bodyNo
no_wakeNo
projectNo
subjectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

D1.3/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 and discloses nothing: not whether this is a write/mutating action, whether it notifies or wakes recipients, what the 'v2 service' implications are, or what happens on failure. 'Execute' hints at mutation but gives no consequences.

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?

One short sentence with no bloat, but it is under-specified rather than concise; the sentence's only content is a restatement of the name plus a version tag.

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 five-parameter mutating tool with zero annotation coverage, no output schema, and undocumented parameters including an ambiguous flag, the description is wholly inadequate to call the tool correctly.

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 five parameters, and the description explains none of them. Semantics for 'to', 'subject', 'body', 'project', and especially 'no_wake' — a non-obvious boolean — are entirely absent, leaving an agent to guess.

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?

The description restates the tool name ('execute bridge send') without naming the resource or verb in plain terms — nothing says this sends a message to a recipient. An agent cannot distinguish it from siblings like bridge_answer or bridge_question based on this text.

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

Usage Guidelines1/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 mention of any alternative tool. The only added phrase, 'through the v2 service', conveys implementation detail rather than selection criteria.

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