Skip to main content
Glama

bridge_context

Adds or shows shared project context so Claude Code and Codex can coordinate tasks, questions, and replies.

Instructions

Execute bridge context 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_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
addNo
showNo
projectNo

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?

No annotations are provided, so the description carries the full burden, yet it discloses nothing about whether this reads or writes state, what permissions it needs, or what happens on invocation. "Execute" is ambiguous and could imply a mutation, leaving the agent unable to assess risk.

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?

It is a single short sentence, so there is no bloat, but brevity here is under-specification rather than economy. The one clause that exists conveys almost no actionable information.

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?

With no annotations, no output schema, and three undocumented parameters, this definition leaves an agent unable to determine what the tool does or how to call it correctly. It is far short of what a three-parameter tool requires.

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?

All three parameters (add, show, project) have 0% schema description coverage, and the description explains none of them. The meanings of "add" (a string) and "show" (a boolean) remain entirely opaque, and their interaction is unspecified.

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 context through the v2 service" restates the tool name with a generic verb ("execute") and an unspecified resource ("context"). It gives no concrete outcome an agent could recognize, and nothing distinguishes it from siblings like bridge_show, bridge_status, or bridge_activity beyond a vague "v2 service" mention.

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 when-to-use guidance, no preconditions, and no mention of alternatives among the many bridge_* siblings. An agent has no basis for choosing this tool over bridge_show or bridge_status.

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