Find Usages
find_usagesIdentify callers and dependencies for a code chunk using incoming, outgoing, or both relationship directions, so you can answer where code is used and what it calls.
Instructions
Find symbol relationships: what calls this code, and what this code calls. Supports incoming (callers), outgoing (dependencies), or both directions. Use after search_code or get_chunk when the user asks 'where is this used?', 'what calls this?', or 'what does this depend on?'. Pass chunk_id from search results.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"chunk_id": "<chunk_id>"
},
"name": "find_usages"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results per direction | |
| chunk_id | Yes | Chunk ID to find usages of | |
| direction | No | incoming = who calls this chunk, outgoing = what this chunk calls, both = both directions | incoming |
| include_hubs | No | When true (default) callers/callees whose own degree is above the group p95 are surfaced with a `[hub]` marker so the agent knows the link is noisy. Set false to drop hub neighbours entirely — useful when probing a specific path through the codebase. | |
| relation_types | No | Filter by relation types (default: all) |