Context+

get_blast_radius

Analyze code dependencies by tracing where a specific symbol is imported or used across files. Helps prevent orphaned code and identifies candidates for inlining before making changes.

Instructions

Before deleting or modifying code, check the BLAST RADIUS. Traces every file and line where a specific symbol (function, class, variable) is imported or used. Prevents orphaned code. Also warns if usage count is low (candidate for inlining).

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": "get_blast_radius"
  }
}

Input Schema

Name	Required	Description	Default
`symbol_name`	Yes	The function, class, or variable name to trace across the codebase.
`file_context`	No	The file where the symbol is defined. Excludes the definition line from results.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.8Mar 24, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries full behavioral burden. It discloses key traits: traces imports AND uses, excludes definition line (via file_context behavior), generates warnings for low usage (inlining candidates), and prevents orphaned code. Missing explicit read-only declaration, though implied by 'get' prefix and 'traces' verb.

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?

Four tightly constructed sentences with zero waste. Front-loaded with usage context (sentence 1), followed by mechanism (sentence 2), and value-add behaviors (sentences 3-4). Every clause earns its place.

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?

No output schema exists, but the description adequately describes conceptual output ('every file and line', usage count warnings). Good coverage for a read-only analysis tool, though explicit mention of return format (e.g., list of locations) would strengthen it.

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 coverage is 100% and descriptions are thorough. The tool description reinforces the semantic types (function, class, variable) but doesn't add syntax details, format constraints, or examples beyond what the schema already provides. Baseline 3 appropriate for high-coverage schemas.

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?

Specific verb ('traces') + resource ('symbol') + scope ('every file and line'). The parenthetical '(function, class, variable)' clarifies the polymorphic input, and the front-loaded context 'Before deleting or modifying code' clearly distinguishes this impact-analysis tool from general search siblings like semantic_code_search.

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?

Explicitly states when to use ('Before deleting or modifying code') and implies workflow integration (safety check). While it doesn't name specific alternatives, the context makes it clear this is for pre-modification validation versus general exploration.

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

Deploy Server