Skip to main content
Glama

Get Call Graph

get_call_graph
Idempotent

Resolve a procedure symbol or address to its canonical entry, then traverse caller or callee relationships in either direction to build the reachable call graph.

Instructions

Resolve one symbol or address to its canonical procedure entry, then traverse the bound provider's caller or callee relationships until the reachable graph is exhausted. Every node uses a canonical address and has an ok/error status; failures use safe typed projections. Unresolved indirect calls may be missing and results are not a whole-program CFG.

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": {
      "address": "0x1000",
      "direction": "forward"
    },
    "name": "get_call_graph"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesA procedure symbol or address to resolve to its canonical entry
directionNoDirection in which to traverse or compare relationships.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the return contract (every node has a canonical address and an ok/error status), failure behavior ('safe typed projections'), and a limitation ('unresolved indirect calls may be missing'). The remaining gap is the provider-binding prerequisite and whether traversal is bounded, which an agent would want to know before calling.

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?

Three dense sentences with the operation front-loaded and the caveats trailing, and no filler. The density of jargon ('canonical procedure entry', 'safe typed projections') costs a little readability but every sentence carries information.

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?

For a two-parameter traversal tool with no output schema, the description supplies the node status model, canonical addressing, and known incompleteness of indirect-call resolution, which is enough for an agent to interpret results. The missing piece is the dependency on a bound provider/session, which is not explained.

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 both parameters are already documented in the schema, and the description adds only indirect meaning by linking 'caller or callee' to traversal direction. It never states explicitly that direction=forward yields callees and backward yields callers, so it does not materially extend 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?

States a concrete verb chain ('resolve one symbol or address to its canonical procedure entry, then traverse... caller or callee relationships') that identifies both the input unit and the output shape. It implicitly separates itself from the path-building siblings by describing exhaustive reachable-graph traversal rather than a single path, but it never names an alternative to disambiguate.

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?

The phrase 'traverse the bound provider's caller or callee relationships until the reachable graph is exhausted' implies the usage context (graph exploration from a seed symbol), and the closing sentence sets a boundary ('results are not a whole-program CFG'). However, there is no explicit when-to-use/when-not guidance against siblings such as build_call_path or trace_call_path, leaving the choice to inference.

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