Skip to main content
Glama

list_functions

Run radare2 analysis to return filtered function lists for binary review, using only_leaf to isolate call-graph leaves for bottom-up analysis.

Instructions

Run radare2 analysis (aa; aflj) and return a filtered function list. only_leaf=true gives call-graph leaves for bottom-up review.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "list_functions"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
limitNo
filterNoRegex on function names
min_sizeNo
only_leafNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful behavior by naming the underlying radare2 commands (aa performs full analysis), implying an expensive operation on the target. It omits whether analysis is read-only, how long it may take, and how failures on non-binaries are reported.

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, front-loaded with the operation and followed by the one non-obvious flag. The parenthetical command notation is compact but slightly cryptic for an agent unfamiliar with radare2.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter tool with no annotations and no output schema, the description is thin: it never indicates what a returned function entry contains (name, size, offset) or the default result cap behavior. Only one parameter and one usage mode are covered, leaving an agent to guess at the rest.

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

Parameters2/5

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

Schema description coverage is only 20% across five parameters, so the description must compensate, but it explains only only_leaf. The regex filter, min_size, limit, and path semantics are left entirely to the schema (and filter's regex behavior is only partly documented there).

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 states a concrete verb+resource: runs radare2 analysis (aa; aflj) and returns a filtered function list. It is clearly distinguishable from binary-inspection siblings such as disassemble_function or imports_exports, though it does not name any alternative explicitly.

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 one hint is that only_leaf=true yields call-graph leaves for bottom-up review, which is a genuine use-case cue. There is no statement of when to prefer this over disassemble_function or triage_binary, and no prerequisites such as the target needing to be a supported binary.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.