Skip to main content
Glama

List Procedures

list_procedures
Idempotent

Lists every analyzed procedure as address/value pairs after provider analysis, distinguishing thunks and external functions so returned addresses can be used in later function operations.

Instructions

List every analyzed procedure as address/value pairs after provider analysis. Ghidra metadata distinguishes thunks and external functions; use returned addresses in later function operations.

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": {},
    "name": "list_procedures"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentNoThe active target's provider document name; use open_binary to switch targets

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false and idempotentHint=true, so the description doesn't need to cover safety. It does add useful domain context that Ghidra metadata marks thunks and external functions, but leaves a notable gap: readOnlyHint=false is counterintuitive for a listing tool, and the description never explains that side effect or whether it triggers provider analysis.

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?

Two tight sentences with no filler, leading with the result shape and following with caveats. Slightly dense but well front-loaded.

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 usefully previews the return format as address/value pairs and flags thunks/externals. For a one-parameter list tool this is close to sufficient, though the unexplained non-read-only annotation remains 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 the single `document` parameter is fully described in the schema, so the baseline applies. The description adds nothing about the document parameter or its default behavior.

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 ("List every analyzed procedure as address/value pairs") and characterizes the output shape. It implicitly contrasts with search_procedures by emphasizing "every," but never names the sibling, so differentiation relies on inference.

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?

Gives a downstream usage hint ("use returned addresses in later function operations") and a precondition ("after provider analysis"), but never states when to pick this over search_procedures or what happens if analysis hasn't run.

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