Skip to main content
Glama

Procedure Callers

procedure_callers
Idempotent

Retrieve a procedure's resolved direct callers by symbol or address from completed static analysis, so you can identify call sites while accounting for unresolved indirect references.

Instructions

Return the provider's resolved direct callers for one procedure identified by symbol or address. Results reflect completed static analysis and may omit unresolved indirect references.

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": {
      "procedure": "main"
    },
    "name": "procedure_callers"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentNoThe active target's provider document name; use open_binary to switch targets
procedureYesThe procedure name or address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Beyond the annotations, the description discloses two meaningful behavioral facts: results depend on completed static analysis, and the caller set can be incomplete because unresolved indirect references are omitted. That is exactly the kind of caveat an agent needs before trusting an empty or short result. It does not reconcile why readOnlyHint is false for what reads like a pure query, which is a minor remaining gap.

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 tight sentences with zero filler, and the core purpose is front-loaded ahead of the completeness caveat. Nothing could be removed without losing information.

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?

There is no output schema, so the description carries the burden of describing the return value, and it only says 'resolved direct callers' without indicating the shape (names, addresses, count, ordering). It also omits any mention of error behavior when the procedure cannot be resolved. Adequate for invoking the tool, incomplete for interpreting its output.

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 document parameter's open_binary switching hint. The description only restates that the procedure can be given as a symbol or an address, adding no format or resolution semantics beyond the schema. Baseline 3 is appropriate.

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?

Uses a specific verb and resource: 'Return the provider's resolved direct callers for one procedure.' The input modes ('identified by symbol or address') and the direct-vs-indirect distinction make the retrieval intent unambiguous. It does not name a sibling such as procedure_callees to contrast against, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to choose this over procedure_callees, procedure_references, or build_call_path. The only implicit routing signal is the caveat that unresolved indirect references may be missing, which hints that a different tool is needed for those, but the agent is left to infer it.

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