impact
Find every direct and indirect caller affected by changing a symbol by tracing the reverse call graph across hops, so you can update all code before refactoring.
Instructions
Trace the blast radius of changing a symbol: starting from the given symbol, walk the reverse call graph — direct callers, their callers, and so on across multiple hops — and return every symbol that could be affected by a change to it. Each affected symbol comes with a depth field (how many hops away it is) and a resolution field naming which index-wide lookup resolved that call edge (e.g. same-file, scoped, global-unique — scoped/global-unique both mean a single matching definition was found index-wide, see docs/mcp-tools.md), so results are grounded in real, resolved call relationships rather than a text search for the symbol's name (which cannot follow more than one hop and cannot tell a real call from a coincidental name match). Use this tool before refactoring — e.g. changing a function's signature or behavior — to find every place in the codebase that may need to change as a result, including indirect callers that a single-hop "find references" would miss. The response can be truncated to fit within a token budget; when it is, truncated is set to true and truncated_count reports how many additional affected symbols were left out. Results come from the local corbel index built by corbel index and only reflect the repository as of the last index run.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| file | No | Optional file path to disambiguate when multiple symbols share this name. | |
| name | Yes | The symbol name to start the impact analysis from. | |
| token_budget | No | Optional cap on the size of the response, in estimated tokens. Defaults to corbel's built-in budget if omitted. |