tzero-mcp

analyze_change_impact

Calculate blast radius and list direct and transitive dependents before modifying a function, class, or symbol to see which modules may break.

Instructions

Calculates blast radius score (0-100) and identifies all direct and transitive dependent modules across the codebase before modifying a specific function, class, or symbol.

Behavior:

Read-only: AST dependency graph traversal; does not modify source files.
Idempotent: Deterministic impact calculation for any given target symbol.
100% Offline: Local AST analysis without remote services.

Usage Guidelines:

When to use: Run BEFORE renaming, refactoring, or modifying a function or class to determine which caller modules could break.
Sibling Routing: For deep recursive caller/callee trees with visual Mermaid graphs, use 'trace_symbol_call_chain'. For file-level module dependencies, use 'query_module_dependencies'.

Returns: Structured Markdown report with blast radius score, risk tier, direct dependents, and transitive impact paths.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`project_root`	No	Workspace root directory containing target symbols (default: current directory).	.
`target_symbol`	Yes	Name of the function, class, or method to analyze for change blast radius.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.1.1Oct 16, 2026

addedInput schema / properties / project_root / description

Added value: +"Workspace root directory containing target symbols (default: current directory)."

addedInput schema / properties / target_symbol / description

Added value: +"Name of the function, class, or method to analyze for change blast radius."

First observedv0.1.0Oct 15, 2026

TDQS

A4.6/5.0

Behavior5/5

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

No annotations are provided, so the description carries the full burden and does so well: it declares read-only AST traversal, deterministic/idempotent results, and 100% offline local analysis with no remote services. These are exactly the behavioral traits an agent needs before invoking a static-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.

Conciseness4/5

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

Front-loaded with the core capability, then logically grouped into Behavior, Usage, and Returns with zero filler sentences. Slight deduction because the Returns block restates a structured output that already exists as an output schema, making it mildly redundant.

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?

For a two-parameter read-only analysis tool, the definition covers purpose, safety profile, invocation timing, alternatives, and return shape. With an output schema present, it does not need to explain return values in detail, so nothing material 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% and both parameters are documented there (target_symbol as the symbol to analyze, project_root with a default of '.'). The description adds no syntax, format, or constraint detail beyond the schema, 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 verb+resource+scope: calculates a blast radius score (0-100) and finds direct/transitive dependents for a function, class, or symbol. It is immediately distinguishable from siblings like trace_symbol_call_chain and query_module_dependencies by naming them explicitly.

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?

Gives a concrete when-to-use trigger ('Run BEFORE renaming, refactoring, or modifying a function or class') and explicit sibling routing for two adjacent alternatives with the condition that selects each (recursive trees/Mermaid vs file-level module deps).

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