Skip to main content
Glama

bridge_agents

Executes agent tasks through the v2 service, enabling Claude Code and Codex on one machine to exchange tasks, questions, reviews, and replies via a shared local SQLite task board.

Instructions

Execute bridge agents through the v2 service.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bridge_agents"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

D1.9/5.0
Behavior1/5

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

With no annotations, the description carries the full behavioral burden and discloses nothing: no side effects, whether execution is synchronous or asynchronous, what auth or setup is required, or what happens on failure. "Execute" implies an action but gives no indication of its consequences or reversibility.

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

Conciseness3/5

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

A single short sentence with no filler, so nothing is wasted. However, its brevity is the result of under-specification rather than tight writing, and the key information is absent rather than front-loaded.

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 tool sitting among 22 similarly named siblings with no annotations, no output schema, and no parameter documentation needs, the description should explain what execution means and when to pick it. It does none of that, leaving an agent unable to call it correctly.

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?

The tool takes zero parameters, so there is no parameter semantics to convey and the schema is self-sufficient. Baseline 4 applies since the description cannot be faulted for missing parameter meaning.

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 with a verb ("Execute bridge agents") and adds the opaque qualifier "through the v2 service." It never explains what a bridge agent is, what execution does, or how this differs from the many sibling tools such as bridge_send or bridge_wake.

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 reference to any alternative among the 22 bridge_* siblings. An agent has no basis for choosing this tool over bridge_send or bridge_wake.

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