MCP Tools
The 6 tools your AI agent gets
One reference page per tool. Tools are exposed via the Model Context Protocol.
For AI engineersThe AI sees these tool descriptions automatically and chooses based on the task. You don't need to memorize them, but understanding the costs helps you debug "why did the AI use the wrong tool".
| Tool | What it does | Token cost |
|---|---|---|
get_project_index | Full project overview at chosen detail level (1-4). Use first. | 1.2K - 24K tokens |
get_file_summary | Symbols + imports for a single file. | 50-200 tokens |
search_symbol | Find where a function/class is defined. | ~30 tokens |
get_impact | List files that depend on a target file. | 50-200 tokens |
get_call_chain | Trace callers and callees of a symbol. | 50-300 tokens |
get_dead_code | Files and functions unreachable from entry points. | 100-1K tokens |
Decision tree for picking a tool
- "What's in this project?" →
get_project_indexat level 1 or 2 - "Where is function X?" →
search_symbol - "What's in file X?" →
get_file_summary - "What if I change file X?" →
get_impact - "What calls function X?" →
get_call_chain - "What's unused?" →
get_dead_code