Skip to main content
Glama

find_callers

Finds all indexed call sites that resolve to a given symbol declaration, returning each match with its resolution quality so you can trace where a function or method is used.

Instructions

Finds indexed call sites whose callee resolved to one declaration. Each result includes its resolution quality.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "repository_root": "<repository_root>",
      "symbol_id": "<symbol_id>"
    },
    "name": "find_callers"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbol_idYesStable indexed symbol ID returned by outline_file or find_symbol.
repository_rootYesAbsolute path to the Git repository root to explore.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does add real signal beyond structured fields — results carry a 'resolution quality,' warning the agent that calls may be unresolved or ambiguous, and 'indexed' hints at an index dependency. It omits whether the tool is strictly read-only, what happens when the symbol is unindexed or has zero callers, and any ordering or size limits.

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 short sentences with zero filler: the operation is front-loaded, followed by the one caveat an agent needs. Nothing is redundant with the schema.

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

Completeness5/5

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

For a two-parameter, read-style lookup with full schema coverage and no output schema, the definition covers the essential shape: what is returned (call sites), the resolution constraint, and the quality signal attached to each result. The remaining gaps (empty results, index staleness) are minor for a tool of this simplicity.

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, including the provenance hint for symbol_id ('returned by outline_file or find_symbol'). The description adds no further parameter meaning, so the baseline 3 applies.

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 specific verb and resource ('Finds indexed call sites') and narrows scope to those 'whose callee resolved to one declaration.' This is far more precise than a restatement of the name, but it never names the sibling it contrasts with (find_callees for the reverse direction, find_references for broader usage).

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: an agent can infer this is the tool for 'who calls this symbol,' and the schema directs it to a symbol_id from find_symbol or outline_file. However, there is no explicit when-to-use versus find_references or find_callees, and no stated prerequisite that the repository must already be indexed.

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