Skip to main content
Glama

bridge_clean

Clean up agent bridge task board records by clearing old or filtered tasks through the v2 service. Supports dry runs to preview removals before applying them.

Instructions

Execute bridge clean 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_clean"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNo
daysNo
statusNo
dry_runNo
projectNo

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 delivers nothing. It does not state whether this deletes or purges data, whether the operation is reversible, whether dry_run defaults to safe mode, or what permissions are required — critical for a 5-parameter tool with a dry_run flag that implies destructive potential.

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 with no wasted clauses, but brevity here comes from under-specification rather than efficiency. The one content-bearing phrase ('v2 service') does little work for the caller.

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 a five-parameter, zero-required, potentially destructive maintenance operation with no annotations and no output schema, the definition supplies nothing an agent needs to invoke it safely or correctly. It is effectively a name echo.

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 five parameters (all, days, status, dry_run, project) and the description mentions none of them. An agent cannot tell whether 'all' overrides 'days'/'status', what values 'status' accepts, or what 'dry_run' returns instead of executing.

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 clean through the v2 service" essentially restates the tool name with a version qualifier. It never says what 'clean' operates on (records, caches, projects, stale entries) or what kind of operation it is, so an agent cannot distinguish it from siblings like bridge_migrate or bridge_export beyond the word 'clean'.

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 guidance on when to use this tool, when not to, or which sibling to prefer for related maintenance tasks. The agent is left to guess entirely from the name.

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