stellarion_get_callees

Answers the question "what does this function call?" by traversing the call graph downward. Shows direct callees and, with increased depth, their callees in turn.

Useful for understanding what a function depends on and what side effects it might trigger.

When to Use

• You want to understand a function's internal dependencies before modifying it
• You need to map out what a function touches (database calls, network requests, etc.)
• You are reviewing unfamiliar code and want to see the full execution tree
• You want to identify potential side effects of calling a function

Parameters

Examples

See what a handler function calls

Natural language:

What functions does handleLogin in src/routes/auth.ts call?

MCP call:

{
  "tool": "stellarion_get_callees",
  "arguments": {
    "uri": "src/routes/auth.ts",
    "line": 23,
    "depth": 1
  }
}

Trace the full execution tree

Natural language:

Show me the complete call tree for processOrder in src/orders/service.py, 4 levels deep

MCP call:

{
  "tool": "stellarion_get_callees",
  "arguments": {
    "uri": "src/orders/service.py",
    "line": 55,
    "depth": 4
  }
}

Audit a function for database calls

Natural language:

What does syncUsers call? I want to see if it hits the database.

MCP call:

{
  "tool": "stellarion_get_callees",
  "arguments": {
    "uri": "src/sync/users.rs",
    "line": 12,
    "depth": 2
  }
}

Output Format

Returns a tree of callee relationships:

• name — Callee function name
• uri — File path of the callee
• line — Line number of the callee definition
• callees — Nested array of transitive callees (up to the requested depth)

Tips

• Use depth: 1 for a quick overview, then increase depth to trace specific branches.
• Combine with stellarion_get_callers for a complete picture of a function's role in the codebase.
• This is especially useful during code review — check what a new function calls to verify it doesn't introduce unexpected dependencies.
• For a combined view of callers, callees, source, and complexity in one call, use stellarion_get_detailed_symbol instead.