Skip to main content
Glama

Procedure Assembly

procedure_assembly
Idempotent

Returns instruction-level assembly for a procedure identified by symbol or hexadecimal address when pseudocode omits calling-convention details; output includes evidence limitations for truncated bodies.

Instructions

Return assembly for one analyzed procedure identified by symbol or hexadecimal address. Use when pseudocode loses calling-convention or instruction-level detail; output is currently returned as one unpaginated string. Ghidra terminal-call assumptions that may cut the analyzed body are reported in Evidence limitations.

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

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.1/5.0
Behavior4/5

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

Adds real context beyond annotations: output is a single unpaginated string (so callers must expect large, non-chunked payloads), and Ghidra terminal-call assumptions can cut the analyzed body, with limitations surfaced in an Evidence section. The one unresolved tension is that the read-verb framing sits oddly with readOnlyHint=false, but the caveat about analysis-altering assumptions partly explains it.

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?

Three sentences, front-loaded with purpose then usage then behavior; no filler. Slightly dense packing of the truncation caveat into the same sentence as the Evidence reference, but every sentence carries 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?

No output schema exists, and the description compensates by describing the return shape (unpaginated string) and a known fidelity limitation. For a 2-parameter read tool this is close to complete, with only size-handling guidance for very large procedures left implicit.

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 parameters are already documented, including the document/target-switching hint. The description only restates that the procedure may be a symbol or hex address, adding little beyond the schema text.

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 ("Return assembly for one analyzed procedure") and pins down the identifier formats ("symbol or hexadecimal address"). The clause about pseudocode losing calling-convention detail separates it from the pseudocode sibling without naming it.

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?

Gives a concrete trigger: use when pseudocode loses calling-convention or instruction-level detail, which implicitly names the alternative (procedure_pseudo_code). No explicit when-not condition or cost warning (e.g. use only for narrow ranges), so it stops short of full routing guidance.

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