Memtrace Relationships

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

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

{ "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

{
  "repo_id": "memdb",
  "target": "validateToken",
  "query_type": "find_callers",
  "depth": 3,
  "file_path": "src/auth.ts"
}

Full parameter spec for every Memtrace tool: references/mcp-parameters.md (bundled at the memtrace-skills plugin root).

Steps

1. Get the symbol name

Use find_symbol or find_code. Save name, scope_path, and file_path from results — pass symbol/target plus optional file_path to graph tools.

2. Choose your approach

Quick 360° view → get_symbol_context (one call).

Targeted traversal → analyze_relationships when you need a specific query_type at custom depth.

3. Interpret results

Use get_symbol_context fields (callers, callees, community, processes) for blast-radius and architecture context. For degree-style metrics on a specific symbol, follow up with get_impact.

4. Follow up

• get_impact(repo_id, target=...) — quantify blast radius
• get_timeline(repo_id, scope_path, file_path) — full version history
• get_evolution(repo_id, from=..., target=...) — window-scoped activity

Output

get_symbol_context returns the symbol's 360° neighbourhood:

{
  "symbol": "validateToken",
  "callers": ["..."],
  "callees": ["..."],
  "type_references": ["..."],
  "community": "...",
  "processes": ["..."],
  "api_callers_cross_repo": ["..."]
}

analyze_relationships returns the symbols/edges matching the requested query_type (no degree metrics — see Common Mistakes).

Common Mistakes