Skip to main content
Glama

blast_radius

Read-onlyIdempotent

Find and count symbol usages across a codebase by kind to assess change impact before refactoring, including call sites and same-name candidates.

Instructions

Find textual usage candidates with counts by kind. Use kind:call for call-containing lines. Includes same-name symbols; use exact_references for binding-resolved TS/JS rename checks.

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

Input Schema

NameRequiredDescriptionDefault
kindNoReturn only this usage kind; totals still show all kinds.
modeNoSummary groups usages by containing symbol (default); detailed returns every matching line.
rootNoAbsolute project root. Omit only where this session started; required elsewhere and on every subagent call.
symbol_nameYesThe function, class, or variable name to trace across the codebase.
file_contextNoThe file where the symbol is defined. Excludes the definition line from results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.0
    • changedInput schema / properties / root / description
      Previous value: -"Absolute project root. Required with linked worktrees; subagents must pass their own worktree root on every call."New value: +"Absolute project root. Omit only where this session started; required elsewhere and on every subagent call."
  2. First observedv1.4.0

TDQS

A4.7/5.0
Behavior4/5

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

Beyond the read-only and non-destructive annotations, it discloses the important behavioral limitation that results are textual candidates and can include unrelated same-name symbols. It also explains the count-by-kind behavior, though it does not mention possible result limits, truncation, or search-scope exclusions.

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?

Three compact sentences front-load the purpose, then provide a practical filtering tip and an important limitation with an alternative. Every sentence contributes actionable information without repetition or unnecessary background.

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?

Together with the fully documented schema and safety annotations, the description supplies what an agent needs to select and invoke this read-only search correctly. It covers the matching model, aggregate counts, a key filtering use case, and the appropriate sibling for precision-sensitive rename analysis.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is already adequate, but the description adds useful semantics for kind:call by specifying call-containing lines. The same-name warning also clarifies that symbol_name is matched textually rather than resolved to a particular binding.

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?

The description uses a specific verb and resource: it finds textual usage candidates for a symbol and provides counts by usage kind. It also distinguishes the tool from exact_references by identifying its textual, same-name matching rather than binding-resolved analysis.

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?

It explicitly directs agents to use kind:call when they need call-containing lines. It also gives a clear alternative and condition: use exact_references for binding-resolved TS/JS rename checks.

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