Skip to main content
Glama

Read Function Instructions

read_function_instructions
Idempotent

Retrieve all raw instructions for an analyzed procedure, including provider-specific text and body extent, and report limitations where Ghidra terminal-call assumptions may cut the body.

Instructions

Return every raw instruction for one analyzed procedure. Instruction text and body extent are provider-specific. Ghidra terminal-call assumptions that may cut the analyzed body are reported in 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": "read_function_instructions"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentNoThe document name
procedureYesThe procedure name or address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond annotations, the description discloses two meaningful behavioral traits: instruction text and body extent are provider-specific (so output shape varies by backend), and Ghidra terminal-call assumptions that may truncate the analyzed body are surfaced in limitations. This prepares the agent for inconsistent output and possible incomplete results, which annotations do not convey.

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?

Three short sentences, each carrying distinct information: the core action is front-loaded, followed by output-variability context and the limitations caveat. No filler or restatement of the name.

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 most of the needed work by explaining what comes back (raw instructions) and warning about provider-specific variability and truncation-limited bodies. It stops short of describing the container structure of the response (e.g., whether instructions come with addresses or ordering), which would fully close the gap.

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%, with procedure name/address and optional document already documented in the schema, so the baseline is 3. The description adds no extra semantics for these parameters, such as accepted address formats or the effect of omitting the document.

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 every raw instruction for one analyzed procedure"), which is clearly distinct from higher-level analysis siblings like analyze_function. It does not explicitly name an alternative, but the "raw instruction" framing makes the scope unambiguous.

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

Usage Guidelines3/5

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

Usage is only implied: the phrase "one analyzed procedure" hints that the procedure must already have been analyzed before calling. There is no explicit when-to-use/when-not guidance, no mention of prerequisites such as needing an open session or target binary, and no routing to alternatives.

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