Skip to main content
Glama

gp_callers

List all callers of a symbol to find dependents before renaming, or all callees to understand dependencies. Uses a pre-indexed reverse map for sub-millisecond results.

Instructions

List every caller of a symbol (direction=callers) or everything it calls (direction=callees). ALWAYS use instead of grep -rn "X(" for "who calls X?" — pre-indexed reverse map, sub-millisecond, no false positives from comments or strings. Use direction=callers to find dependents before a rename; direction=callees to understand what a function depends on. Do NOT use for full blast-radius analysis across multiple hops — use gp_impact instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesSymbol name or full id.
directionNoDefault 'callers'.
limitNoMax edges (default 50).
includeUnresolvedNoInclude external/stdlib calls (default true).
pathNoRepo root with a GraphPilot index. Optional: when omitted, resolves via GRAPHPILOT_ROOT, MCP workspace roots, parent walk, or a single ~/.graphpilot index.
Behavior3/5

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

Mentions sub-millisecond speed and no false positives, but lacks explicit statement of read-only nature or side effects; no annotations to compensate.

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

Conciseness5/5

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

Two concise sentences plus note; front-loaded with core action and efficient.

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

Completeness3/5

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

Covers core functionality and use cases, but lacks description of output format (list structure) given no output schema.

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 coverage is 100%, so baseline 3. Description adds no extra parameter info beyond what schema provides.

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

Purpose5/5

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

Clearly states it lists callers or callees of a symbol, distinguishes from sibling gp_impact by noting multi-hop analysis.

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

Usage Guidelines5/5

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

Explicitly says when to use (e.g., before rename) and when not to use (full blast-radius), even recommends alternative tool gp_impact.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/graphpilot-oss/graphpilot'

If you have feedback or need assistance with the MCP directory API, please join our Discord server