Skip to main content
Glama

impact

Read-onlyIdempotent

Analyze a file's change blast radius: list dependents by depth, count affected files, and identify which files to read first before editing.

Instructions

Blast radius of changing a file: dependents by depth, counts, and the files to read first.

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": {
      "target": "<target>"
    },
    "name": "impact"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNoList everything instead of stopping at 200 items.
depthNoHow many hops to follow.
targetYesFile path relative to the repository root, or a module ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description does add value by disclosing what the result contains (depth-stratified dependents, counts, prioritized files), which matters since no output schema exists. It omits the 200-item truncation behavior implied by the 'all' parameter, so it adds context but not a complete behavioral picture.

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?

A single compact sentence with zero waste, front-loading the core concept before the output enumeration. It is slightly elliptical — a noun phrase rather than a verb phrase — which makes it marginally less immediately actionable, but nothing is superfluous.

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?

With a fully documented three-parameter schema, rich annotations, and no output schema, the description just needs to convey what the tool computes and roughly what comes back, which it does. The only real gap is the absence of guidance on when to reach for this versus dependency-listing siblings, a minor omission given how self-describing the parameters are.

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%, and every parameter (target, depth, all) carries its own inline documentation including defaults, bounds, and the 200-item behavior. The description's 'by depth' hints at the depth parameter's effect but adds no syntax or format details beyond what the schema already states, so the baseline of 3 applies.

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 a specific analytical concept ('blast radius of changing a file') and enumerates the outputs it produces: dependents by depth, counts, and files to read first. That is far more specific than a bare 'impact' label and lets an agent distinguish it from simple dependency lookups like deps or rdeps. It stops short of explicitly contrasting itself with any sibling, so it lands at 4 rather than 5.

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

Usage Guidelines3/5

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

Usage is only implied: the phrase 'files to read first' signals a pre-change triage scenario, and 'blast radius of changing a file' implies you call it before editing. There is no explicit when-to-use statement, no condition selecting this over siblings such as usages or find_callers, and no prerequisites or exclusions.

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