Skip to main content
Glama
Sign In
codex-claude-bridge-mcp

codex-claude-bridge-mcp

by nevzoom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

post_message

Send a message to another agent, optionally linked to a task, to coordinate through the shared task board and message inbox.

Instructions

Send a message to the other agent, optionally attached to a task.

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>",
      "text": "<text>"
    },
    "name": "post_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromYes
textYes
task_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It states the action and the optional task association, but omits important details such as how 'from' and 'to' work, whether messages are persisted, delivery guarantees, or any side effects.

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?

The description is a concise, single sentence that effectively front-loads the core action and the one optional modifier. Every word contributes, and no unnecessary detail is present.

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

Completeness2/5

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

For a tool with four parameters, no output schema, and no annotations, the description is too sparse. It does not clarify the relationship between sender and recipients, how the task attachment is used, or how this tool fits with read_messages and task-management siblings. An agent would likely need external knowledge to invoke it correctly.

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

Parameters2/5

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

The input schema has no descriptions (0% coverage), so the description must compensate. It mentions 'attached to a task' which clarifies task_id, but does not explain the semantics of 'from' and 'to', nor does it add meaning to 'text' beyond the schema's minLength.

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?

The description clearly states the tool's function: sending a message to another agent, with an optional task attachment. This distinguishes it from sibling tools like read_messages (reading) and task-management tools.

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

Usage Guidelines3/5

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

The description implies the usage: use this to send messages to another agent, optionally tied to a task. However, it does not explicitly mention when to prefer this over alternatives like read_messages, nor does it state exclusions or prerequisites.

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

Deploy Server

Other Tools