Navigation Tools
Navigation tools help your AI assistant trace how code connects. They query the knowledge graph built during indexing to answer questions about who calls what, what depends on what, how data flows through functions, and which entry points reach a given symbol.
call_graph_query
Section titled “call_graph_query”Query the call graph for a symbol. Returns the callers or callees of a function or method, traversing the graph to the specified depth.
Parameters
Section titled “Parameters”| Name | Type | Required | Description |
|---|---|---|---|
fqn |
string | Yes | Fully qualified name of the symbol |
direction |
string | Yes | callers (who calls this) or callees (what this calls) |
depth |
integer | No | How many levels to traverse (default: 3) |
workspace_id |
string | No | Limit results to a specific workspace |
repo_id |
string | No | Limit results to a specific repository |
Example prompt
Section titled “Example prompt”“Who calls the processPayment method?”
The assistant calls call_graph_query with direction callers and returns a tree of all functions that directly or transitively call the target method, showing the call chain from entry point to implementation.
dependency_graph
Section titled “dependency_graph”Get the dependency graph for a module or package. Returns upstream or downstream dependencies, showing what the module depends on or what depends on it.
Parameters
Section titled “Parameters”| Name | Type | Required | Description |
|---|---|---|---|
module_path |
string | Yes | Path to the module or package |
direction |
string | No | upstream (what this depends on) or downstream (what depends on this). Default: downstream |
depth |
integer | No | How many levels to traverse (default: 2) |
workspace_id |
string | No | Limit results to a specific workspace |
repo_id |
string | No | Limit results to a specific repository |
Example prompt
Section titled “Example prompt”“What depends on the auth package?”
The assistant calls dependency_graph with direction downstream and returns all modules that import or depend on the auth package, helping you understand the blast radius of changes to that package.
data_flow_trace
Section titled “data_flow_trace”Trace data flow through function parameters and return values. Shows how a value propagates through the call chain - from where it enters the system to where it is consumed.
Parameters
Section titled “Parameters”| Name | Type | Required | Description |
|---|---|---|---|
fqn |
string | Yes | Fully qualified name of the symbol to trace |
workspace_id |
string | No | Limit results to a specific workspace |
repo_id |
string | No | Limit results to a specific repository |
Example prompt
Section titled “Example prompt”“Where does the userId parameter flow to?”
The assistant calls data_flow_trace and returns the path that data takes through the codebase - from the function parameter through intermediate transformations to its final destinations, such as database queries or API responses.
entry_point_map
Section titled “entry_point_map”Find entry points that lead to a symbol. Entry points are the external interfaces of your application - HTTP routes, CLI commands, event handlers, scheduled jobs - that ultimately invoke the target symbol.
Parameters
Section titled “Parameters”| Name | Type | Required | Description |
|---|---|---|---|
fqn |
string | Yes | Fully qualified name of the symbol |
workspace_id |
string | No | Limit results to a specific workspace |
repo_id |
string | No | Limit results to a specific repository |
Example prompt
Section titled “Example prompt”“What HTTP endpoints reach the UserRepository?”
The assistant calls entry_point_map and returns all entry points (routes, handlers, commands) that transitively invoke methods on the UserRepository, helping you understand which external interfaces are affected by changes to that class.