Skip to main content
Glama

bridge_export

Exports bridge task data to a specified destination via the v2 service, enabling transfer of shared task board records between Claude Code and Codex.

Instructions

Execute bridge export 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": {
      "destination": "<destination>"
    },
    "name": "bridge_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
destinationYes

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?

With no annotations supplied, the description carries the full behavioral burden, yet it discloses nothing about side effects, whether files are written, what permissions are required, or whether the operation is read-only. "Execute" implies an action but leaves its consequences entirely opaque.

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?

The single sentence is short but under-specified rather than concise; it spends its words on a tautological restatement and an unhelpful implementation reference. Front-loading is moot because there is no substantive content to front-load.

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 an export operation with an undocumented required destination, no annotations, and no output schema, the description should explain the target format, the data being exported, and the response. None of that is present, leaving an agent unable to invoke the tool 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?

There is one required parameter, "destination", with 0% schema description coverage, and the description says nothing about what it means. Whether it is a filesystem path, URL, identifier, or service name is left completely undetermined, which is a critical gap for a required argument.

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 export through the v2 service" essentially restates the tool name (bridge_export) with no added specificity: no indication of what is exported, from where, or in what form. The phrase "v2 service" hints at an implementation detail rather than telling an agent what the tool accomplishes, and nothing distinguishes it from siblings such as bridge_activity or bridge_log.

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?

The description contains no when-to-use guidance, no prerequisites, and no reference to any alternative among the many bridge_* siblings. An agent cannot infer under what circumstances exporting is appropriate versus using 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.