tracer
Read-only
Trace code execution flow or map structural dependencies to analyze method calls, call chains, and architecture.
Instructions
Performs systematic code tracing with modes for execution flow or dependency mapping. Use for method execution analysis, call chain tracing, dependency mapping, and architectural understanding. Supports precision mode (execution flow) and dependencies mode (structural relationships).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| step | Yes | Current work step content and findings from your overall work | |
| model | Yes | Currently in auto model selection mode. CRITICAL: When the user names a model, you MUST use that exact name unless the server rejects it. If no model is provided, you may use the `listmodels` tool to review options and select an appropriate match. Top models: gemini-2.5-pro (score 100, 1.0M ctx, thinking, code-gen); gemini-3-pro-preview (score 100, 1.0M ctx, thinking, code-gen); gemini-2.5-flash (score 61, 1.0M ctx, thinking); gemini-2.0-flash (score 56, 1.0M ctx, thinking); gemini-2.0-flash-lite (score 42, 1.0M ctx). | |
| images | No | Optional paths to architecture diagrams or flow charts that help understand the tracing context. | |
| findings | Yes | Important findings, evidence and insights discovered in this step | |
| confidence | No | Confidence level: exploring (just starting), low (early investigation), medium (some evidence), high (strong evidence), very_high (comprehensive understanding), almost_certain (near complete confidence), certain (100% confidence locally - no external validation needed) | |
| trace_mode | Yes | Type of tracing: 'ask' (default - prompts user to choose mode), 'precision' (execution flow) or 'dependencies' (structural relationships) | |
| step_number | Yes | Current step number in work sequence (starts at 1) | |
| total_steps | Yes | Estimated total steps needed to complete work | |
| files_checked | No | List of files examined during this work step | |
| relevant_files | No | Files identified as relevant to issue/goal (FULL absolute paths to real files/folders - DO NOT SHORTEN) | |
| continuation_id | No | Unique thread continuation ID for multi-turn conversations. Works across different tools. ALWAYS reuse the last continuation_id you were given—this preserves full conversation context, files, and findings so the agent can resume seamlessly. | |
| relevant_context | No | Methods/functions identified as involved in the issue | |
| next_step_required | Yes | Whether another work step is needed. When false, aim to reduce total_steps to match step_number to avoid mismatch. | |
| target_description | Yes | Description of what to trace and WHY. Include context about what you're trying to understand or analyze. | |
| use_assistant_model | No | Use assistant model for expert analysis after workflow steps. False skips expert analysis, relies solely on your personal investigation. Defaults to True for comprehensive validation. |