Skip to main content
Glama

find_callers

Read-only

Lists every direct call site of a function or class, showing caller, location, and callee so you can inspect usage before changing a signature or behavior.

Instructions

Who calls this? Lists every call to the definitions matching name: the calling symbol, its kind, the repository, path and line of the call, and which definition is called. Use it before changing a function's signature or behavior, to see its direct call sites. For everything a change could reach through chains of calls, use impact_of; for what this symbol itself calls, use find_callees. Calls come from the parse tree, so comments, docstrings and strings never count. A call at module level has kind file and name (module). At most 200 rows; truncated is true when more exist. Next step: get_symbol on a caller to read it.

Input Schema

NameRequiredDescriptionDefault
nameYesA bare name (url_for), which matches url_for and every Class.url_for, or a qualified name (Flask.url_for), which matches only that definition. Case-sensitive.
repoNoLook only in this registered repository, for example flask. list_repositories gives the valid names. Default: all repositories.

Output Schema

NameRequiredDescriptionDefault
reasonYes
statusYes
resultsYes
truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.2

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true; the description adds substantial context beyond that: results come from the parse tree so comments/docstrings/strings never match, module-level calls are reported as kind 'file' with name '(module)', and results are capped at 200 rows with a 'truncated' flag. These are exactly the behavioral facts an agent needs before trusting or paging results.

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?

Front-loaded with the question and the core behavior, then grouped into return fields, usage, sibling routing, a correctness caveat, limits, and next step. Every sentence carries distinct information with no redundancy.

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?

Output schema exists, yet the description still signals the row shape and truncation semantics; combined with explicit sibling routing and next-step guidance, an agent has everything needed to call it correctly and interpret the response.

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 (bare vs qualified name matching, repo scoping) are already fully documented in the schema. The description says only 'definitions matching name' and adds no matching syntax or repo semantics of its own, which is the expected baseline when the schema carries the load.

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?

Opens with a concrete question and a specific verb+resource ('Lists every call to the definitions matching name'), then enumerates exactly what each row contains. It explicitly names what it is not (impact_of, find_callees), so the agent can distinguish it from siblings without opening a schema.

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?

States both when to use it ('before changing a function's signature or behavior, to see its direct call sites') and the two alternatives with the condition that selects each: impact_of for transitive reach, find_callees for outgoing calls. There is also a stated next step (get_symbol on a caller).

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