Skip to main content
Glama

Procedure Pseudo Code

procedure_pseudo_code
Idempotent

Decompile an analyzed procedure by symbol name or address to get provider-specific pseudocode; use procedure_assembly when instruction precision matters.

Instructions

Decompile one analyzed procedure by symbol name or provider-normalized address. Returns provider-specific pseudocode, never original source or cross-provider text equivalence, and may return null; request procedure_assembly when instruction precision matters. Ghidra no-return assumptions may cut the analyzed body; Evidence limitations report observed terminal calls and available callee identities.

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

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.6/5.0
Behavior5/5

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

Beyond the annotations it discloses substantial behavior: output is provider-specific pseudocode, never original source, has no cross-provider text equivalence, may be null, and Ghidra no-return assumptions can truncate the analyzed body. It also flags evidence limitations around terminal calls and callee identities — caveats an agent cannot get from the structured fields.

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 core action and identifier forms, then caveats and the sibling hand-off; no filler sentences. The final clause about evidence limitations is dense and slightly cryptic, costing a point.

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 tool with no output schema, the definition covers what is returned, its provider-specific nature, null possibility, truncation risk, and the alternative tool. Nothing an agent needs in order to call and interpret it correctly appears missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning by specifying that addresses must be provider-normalized and that identifiers may be symbols. It does not elaborate on the document parameter, which the schema already explains.

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?

States a specific verb and resource ('Decompile one analyzed procedure') plus the accepted identifier forms ('symbol name or provider-normalized address'), and explicitly distinguishes the output from procedure_assembly's instruction-level view. An agent can tell it apart from siblings without opening any schema.

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?

Explicitly routes the agent to procedure_assembly 'when instruction precision matters', which is a concrete when-to-use-else rule. It does not state prerequisites beyond the implicit 'analyzed procedure' and gives no when-not-to-use conditions for the null case.

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