Skip to main content
Glama

Trace Call Path

trace_call_path

Trace direct callers or callees from a start symbol or address, optionally toward a goal, resolving canonical entries and returning visited nodes, edges, and shortest path.

Instructions

Resolve start and optional goal symbols or addresses to canonical procedure entries, then trace direct callers or callees until the graph is exhausted or the goal is reached. Results use canonical addresses; Evidence preserves supplied selectors. Returns visited nodes, direct-call edges, a shortest traversal path, provider failures, and residual unknowns. A requested goal is unknown when unresolved expansions prevent proving it absent; unresolved indirect calls remain unknown.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "goal": "0x1100",
      "start": "0x1000",
      "direction": "forward"
    },
    "name": "trace_call_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalNoAn optional destination procedure symbol or address
startYesA starting procedure symbol or address
directionNoDirection in which to traverse or compare relationships.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds substantial behavioral context beyond the annotations: canonical address output, evidence preserving supplied selectors, returned visited nodes and direct-call edges, shortest traversal path, provider failures, and residual unknowns. It also explains the important unknown-goal semantics when unresolved expansions prevent proving absence. The annotations do not conflict with this tracing behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but front-loaded, first stating the core resolve-and-trace action and then summarizing outputs and unknown handling. It is appropriately sized for a graph traversal tool, though the wording is somewhat jargon-heavy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of explaining return values, and it does so by listing visited nodes, edges, shortest path, provider failures, and residual unknowns. It is complete for invocation and interpretation, with the main gap being lack of sibling-tool routing guidance.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents start, goal, and direction. The description adds that start and goal are resolved to canonical procedure entries and that traversal follows callers or callees, but it does not explicitly map forward/backward direction semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: resolve start/goal symbols or addresses, then trace direct callers or callees. It clearly describes the traversal behavior, but it does not explicitly distinguish this tool from similarly named siblings such as build_call_path or get_call_graph.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the description of tracing callers/callees until the graph is exhausted or a goal is reached. However, there is no explicit when-to-use guidance, no exclusions, and no named alternative for related call-graph tasks.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools