Skip to main content
Glama

Synapse

What breaks if this changes

blast_radius
Read-onlyIdempotent

Every call site of a file or one of its functions, with the calling line of code, plus importers and tests. Use before changing a signature or deleting code.

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": {
      "path": "<path>",
      "repository": "<repository>"
    },
    "name": "blast_radius"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesRepo-relative file path.
symbolNoOptional function/class/method name in that file.
repositoryYesPublic GitHub repository as "owner/name" (e.g. "pallets/flask") or its github.com URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to say what comes back, and it does: call sites with the calling line of code, importers, and tests. With no output schema, that result-shape disclosure is the key added value. It omits whether results are truncated, ranked, or limited by repo size, which matters for a cross-repository analysis tool.

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

Conciseness5/5

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

Two sentences, no filler, and the output contents are front-loaded ahead of the usage trigger. Every clause carries information an agent needs.

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

Completeness4/5

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

For a three-parameter read-only analysis tool with no output schema, the definition states purpose, scope, return contents, and the moment to call it. Gaps remain around result size limits, supported languages, and whether private repos are excluded, but nothing essential to invoking it correctly is missing.

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 the schema already documents path, symbol, and repository format. The phrase "a file or one of its functions" does quietly convey that the optional symbol narrows results from file-level to function-level call sites, which is a small addition. Otherwise the description adds no format or constraint detail beyond the schema, matching the baseline for full coverage.

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

Purpose4/5

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

The description names the exact resource and output: every call site of a file or one of its functions, with calling lines, plus importers and tests. That is far more specific than the title and lets an agent distinguish it from siblings like read_code or find_existing. It stops short of a 5 because it never explicitly contrasts itself with tests_for, whose territory (tests) it partially overlaps.

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

Usage Guidelines4/5

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

"Use before changing a signature or deleting code" gives a concrete triggering condition tied to a development workflow. There are no explicit exclusions or named alternatives, so the agent must infer when read_code or tests_for would be the better call, but the when-to-use signal is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources