memtrace-relationshipslisted

## Overview Traverse the code knowledge graph to map relationships between symbols — callers, callees, class hierarchies, imports, exports, and type usages. Essential for understanding a symbol's neighbourhood before modifying it. ## Quick Reference | query_type | What it finds | |------------|---------------| | `find_callers` | What calls this function/method? | | `find_callees` | What does this function call? | | `class_hierarchy` | Parent classes, interfaces, mixins | | `overrides` | Which child classes override this method? | | `imports` | What modules does this file import? | | `exporters` | Which files import this module? | | `type_usages` | Where is this type/interface referenced? | > **Parameter types:** Numbers (`depth`, etc.) must be JSON numbers — not strings. ## Graph tool parameters ### `get_symbol_context` (360° view — prefer this first) Required: `repo_id`, `symbol` ```json { "repo_id": "memdb", "symbol": "validateToken", "file_path": "src/auth.ts" } ``` Returns: callers, callees, type references, community, processes, cross-repo API callers. ### `analyze_relationships` (targeted traversal) Required: `repo_id`, `target`, `query_type` ```json { "repo_id": "memdb", "target": "validateToken", "query_type": "find_callers", "depth": 3, "file_path": "src/auth.ts" } ``` | Param | Default | Notes | |---|---|---| | `depth` | **3** (max 10) | Not 2 | | `file_path` | — | Disambiguates overloaded names | Full parameter spec for every Memtrace tool: