Skip to main content
Glama

Collide MCP

by com.collidemcp.api
OverviewDiscussionsAdmin

blast_radius

Read-only

Before renaming, changing a signature or deleting: every symbol that depends on this one, level by level, with each dependent's file, owner and any in-flight work over it. Answers "what breaks if I change this" from the live code graph; skip it when the briefing's Coverage line says every dependent is already listed. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesRepo-relative file path of the symbol.
depthNoHow many hops of dependents to follow, 1 to 6 (default 3).
symbolNoThe symbol whose dependents to list; omit for the whole file.
repo_idNoThe repository id, e.g. github.com/org/repo (the Collide briefing names it). Omit it to use the repo your session works in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / repo_id / description
      Previous value: -"The repository id, e.g. github.com/org/repo (repo_id in .collide/config.json)."New value: +"The repository id, e.g. github.com/org/repo (the Collide briefing names it). Omit it to use the repo your session works in."
    • changedInput schema / required
      Previous value: -[
-  "repo_id",
-  "path"
-]New value: +[
+  "path"
+]
  2. Changed4 schema fields changed
    • addedInput schema / properties / depth / description
      Added value: +"How many hops of dependents to follow, 1 to 6 (default 3)."
    • addedInput schema / properties / path / description
      Added value: +"Repo-relative file path of the symbol."
    • addedInput schema / properties / repo_id / description
      Added value: +"The repository id, e.g. github.com/org/repo (repo_id in .collide/config.json)."
    • addedInput schema / properties / symbol / description
      Added value: +"The symbol whose dependents to list; omit for the whole file."
  3. Changed10 schema fields changed
    • removedInput schema / properties / depth / default
      Removed value: -3
    • removedInput schema / properties / depth / title
      Removed value: -"Depth"
    • removedInput schema / properties / path / description
      Removed value: -"Repo-relative file path, e.g. src/app/api.py."
    • removedInput schema / properties / path / title
      Removed value: -"Path"
    • removedInput schema / properties / repo_id / description
      Removed value: -"Repository id — the git remote (e.g. github.com/acme/api) or a bare folder name; a #branch suffix scopes to that branch."
    • removedInput schema / properties / repo_id / title
      Removed value: -"Repo Id"
    • removedInput schema / properties / symbol / default
      Removed value: -""
    • removedInput schema / properties / symbol / description
      Removed value: -"A symbol in the file — function, class, method, or constant name."
    • removedInput schema / properties / symbol / title
      Removed value: -"Symbol"
    • removedInput schema / title
      Removed value: -"blast_radiusArguments"
  4. Added

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description's 'Read-only' is largely redundant. It does add value beyond the annotations by disclosing the data source (live code graph), the freshness of in-flight work data, and a completeness caveat tied to briefing coverage.

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

Conciseness4/5

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

The tool is front-loaded with the trigger scenario before the output description, and the skip-condition is placed last where it belongs. The colon-fragment opening is slightly awkward, but every sentence carries information and nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description takes on the burden of describing the return content — dependents at each level plus file, owner and in-flight work — and it does so completely. Combined with the usage and coverage caveats, an agent has everything needed to call and interpret this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all four parameters are already documented in the schema. The description only faintly gestures at them ('this one' for symbol, 'level by level' for depth) without adding syntax, defaults, or format guidance, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and scope: every symbol that depends on this one, level by level, with each dependent's file, owner and in-flight work. This is clearly distinguishable from siblings like get_symbol and explain_code, and the phrasing 'what breaks if I change this' anchors the intent unmistakably.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit trigger conditions ('Before renaming, changing a signature or deleting') and an explicit when-not ('skip it when the briefing's Coverage line says every dependent is already listed'), which also routes the agent to sibling get_briefing. Nothing is left to inference.

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

All Collide MCP toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources