Skip to main content
Glama

bridge_migrate

Migrates bridge task-board data through the v2 service using a specified source, enabling shared task exchanges to be updated.

Instructions

Execute bridge migrate 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": {
      "source": "<source>"
    },
    "name": "bridge_migrate"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYes

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 and discloses nothing: it does not say whether the operation is destructive, whether it is reversible, what permissions are required, whether it is idempotent, or what happens on failure. For a tool named "migrate" that almost certainly mutates state, this is a serious gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no wasted clauses, but the brevity comes from omission rather than economy — nothing is front-loaded because nothing substantive is said.

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 an undocumented required parameter, the description would need to explain the migration's effect and return behavior. It explains neither, leaving an agent unable to call the tool correctly or safely.

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% and the single required parameter "source" is undocumented in both schema and description. The description does not explain what a valid source looks like (a path, an ID, a URL, a version tag) or what constraints apply.

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?

The description restates the tool name ("bridge migrate") with the generic verb "Execute" and adds only "through the v2 service." It never says what is being migrated or what a migration produces, so it is close to tautology and gives an agent no basis for distinguishing it from the other bridge_* tools.

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 prerequisites, and no mention of alternatives or when not to call it. The phrase "through the v2 service" is not actionable usage context.

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