Skip to main content
Glama

Procedure Callees

procedure_callees
Idempotent

Return resolved direct callees for one procedure by symbol or address to map call relationships; unresolved indirect calls may be absent, so verify edge uncertainty with analysis and typed references.

Instructions

Return the provider's resolved direct callees for one procedure identified by symbol or address. Unresolved indirect calls may be absent; use analyze_function and typed references to preserve available edge uncertainty.

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_callees"
  }
}

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

A4/5.0
Behavior4/5

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

The key behavioral caveat is disclosed: results are limited to resolved direct callees and 'unresolved indirect calls may be absent'. That is exactly the kind of limitation annotations cannot convey. It stops short of describing ordering, completeness guarantees, or whether the response is paginated.

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 sentences, front-loaded with the core action and scope, followed by the uncertainty caveat and fallback. No filler or redundancy.

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?

With no output schema, the description does not describe what a returned callee edge looks like or whether unresolved edges appear as null/unknown markers. It compensates for the more important gap by warning that indirect edges may be missing and pointing to alternatives.

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 both the procedure and document parameters are already documented, including the note to use open_binary to switch targets. The phrase 'identified by symbol or address' restates the schema rather than adding resolution rules or accepted address formats.

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?

The description names a specific verb and resource ('Return the provider's resolved direct callees') and scopes it to 'one procedure identified by symbol or address'. That is enough to separate it conceptually from procedure_callers (inverse direction) and procedure_references, though it never names a sibling explicitly.

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

Usage Guidelines4/5

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

It gives an explicit fallback path: when edges are unresolved or indirect, 'use analyze_function and typed references' to preserve uncertainty. That is real when-to-use guidance, but there is no statement of when not to use this tool in favor of procedure_callers or build_call_path.

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