Skip to main content
Glama

bridge_project

Create, list, or inspect projects through the v2 service to organize shared task exchange between Claude Code and Codex agents.

Instructions

Execute bridge project 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": {
      "action": "<action>"
    },
    "name": "bridge_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalNo
nameNo
actionYes
workspaceNo

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 init mutates workspace state, whether list/show are read-only, what permissions are needed, or what gets created on init. The one behavioral claim it makes (v2 service execution) does not map onto any of the declared actions.

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 short, but brevity here is under-specification rather than economy. The single clause spends its words on "through the v2 service," which gives an agent nothing actionable, while omitting the one thing that matters, the action enum.

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?

A four-parameter tool with a required discriminator enum, zero schema descriptions, no annotations, and no output schema needs a description that explains each action and its required inputs. This one sentence covers none of that, leaving an agent unable to choose an action or populate parameters 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 four parameters, and the description mentions none of them. goal, name, and workspace are entirely undocumented, and the description does not even hint that action selects among init/list/show or which parameters each action requires.

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 project" restates the tool name with a generic verb, and "through the v2 service" is implementation detail rather than purpose. It also misleads: the schema's actions are init/list/show, which are setup and read operations, not anything an agent would call "execute". Nothing distinguishes it from siblings like bridge_show or bridge_status.

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 exclusions, and no named alternative. Worse, the verb "execute" implies a run/write operation while the enum offers init/list/show, so the only usage signal present points an agent in the wrong direction.

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