Skip to main content
Glama

Procedure Info

procedure_info
Idempotent

Retrieve metadata for a single procedure by symbol or address, including entrypoint, signature, locals, size, block count, and observed body ranges.

Instructions

Return provider metadata for one procedure identified by symbol or address: entrypoint, signature, locals, size, block count, and complete inclusive body ranges when observed. Extents reflect the provider's analyzed body; Ghidra terminal-call assumptions that may cut it are reported in Evidence limitations. Hopper locals preserve observed names and signed stack displacements; source types remain unknown. Body byte count and enclosing span remain distinct; unavailable extent is explicit.

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

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?

Annotations only declare idempotent/destructive/openWorld flags, so the description must carry the semantic burden, and it does: it discloses provider-dependent behavior (Ghidra terminal-call assumptions reported in Evidence limitations; Hopper locals preserving names and signed displacements with source types unknown), the distinction between body byte count and enclosing span, and explicit signaling of unavailable extents. This is unusually rich caveat disclosure. Note the annotations set readOnlyHint=false even though the description frames this as a pure metadata read — not a direct contradiction, but an inconsistency an agent may trip over.

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

Conciseness4/5

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

Front-loaded with the return payload, then progressively narrower caveats, with no filler or restatement of the title. The final two sentences are telegraphic to the point of being terse ('Body byte count and enclosing span remain distinct; unavailable extent is explicit'), costing some readability, but every sentence carries distinct information.

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 correctly takes on the job of enumerating return fields and their caveats, so an agent knows what it will get. It is complete for the happy path; the remaining gap is failure/ambiguity behavior (unknown symbol, ambiguous match), which the tool surface leaves unaddressed.

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% and both parameters are documented, including the document parameter pointing at open_binary for switching targets. The description adds only the clarification that a procedure may be identified by symbol or address, which reinforces the schema rather than extending it. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Return provider metadata for one procedure') and enumerates exactly what metadata comes back: entrypoint, signature, locals, size, block count, body ranges. That field list implicitly separates it from siblings like procedure_assembly, procedure_pseudo_code, and procedure_callees/callers. It stops short of naming any sibling, so an agent must infer the boundary rather than being told it.

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?

The description never says when to reach for this tool versus the many procedure_* siblings, nor does it name an alternative or an exclusion. Guidance is only inferable from the field enumeration ('this is the metadata tool, not the code tool'). There is also no mention of behavior when the symbol is ambiguous or absent.

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