BCD — Bridge Control Delegate

send_message

Send a message to another AI agent on this BCD account by its name from list_agents, or to every agent with to: "*". Use it to hand over work, ask a question or report back. The receiver reads it with check_inbox when it next looks, so say what you need and by when. Never include passwords, keys or other secrets.

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": {
      "from": "<from>",
      "to": "<to>",
      "message": "<message>"
    },
    "name": "send_message"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	The receiving agent's name, or * for every agent
`from`	Yes	Your agent name
`message`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations only declare non-read-only, non-destructive, non-open-world. The description adds the genuinely useful behavior: delivery is asynchronous ('the receiver reads it with check_inbox when it next looks'), '*' broadcasts to every agent, and a safety constraint bans secrets in message content. It does not address failure modes such as an unknown recipient name.

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?

Four short sentences, front-loaded with the addressing rule before the motivation and the safety caveat. Every sentence carries distinct information (target, purpose, delivery timing, content rule) with no filler.

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

Completeness4/5

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

No output schema exists, and the description covers the key unknowns: how the recipient retrieves the message and how broadcast works. For a three-parameter fire-and-forget send it is nearly complete; only what happens on an invalid recipient or whether send success is confirmed is left unstated.

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?

Schema coverage is 67% and the message parameter has no schema description; the description compensates with content guidance ('say what you need and by when') and a prohibition on secrets. It also restates the '*' broadcast value for 'to', which the schema already documents, so some value is redundant.

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

Purpose5/5

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

States a specific verb (send), resource (message), and target (another AI agent by name, or all agents via '*'), and cross-references the sibling list_agents that supplies valid names. An agent can distinguish this from check_inbox and send_feedback without opening any schema.

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 concrete use cases (hand over work, ask a question, report back) and names the receiving counterpart check_inbox, which tells the agent how the message gets consumed. It stops short of explicit exclusions or a 'when not to use this' clause, so it is clear context rather than full routing guidance.

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

All BCD — Bridge Control Delegate tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?