Skip to main content
Glama

List Names

list_names
Idempotent

Lists every analyzed memory and external symbol as address/value pairs, including provider metadata that distinguishes Ghidra primary, dynamic, external, type, and source facts.

Instructions

List every analyzed memory and external symbol as address/value pairs. Provider metadata distinguishes Ghidra primary, dynamic, external, type, and source facts when available.

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

Input Schema

NameRequiredDescriptionDefault
addressNoA provider-normalized address; default memory uses 0x-prefixed hexadecimal
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

B3.2/5.0
Behavior3/5

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

Annotations already supply the safety profile (destructive=false, idempotent=true, openWorld=false), so the description's main added value is the note that provider metadata carries Ghidra primary/dynamic/external/type/source distinctions 'when available' — useful context about result heterogeneity. It does not explain why readOnlyHint is false for a listing operation, nor whether results are complete or capped, which leaves a mild tension between 'List' and the non-read-only annotation unaddressed.

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 sentences, front-loaded with the core action and result shape, with the metadata caveat second. The second sentence is dense with provider jargon but every clause carries real information, so no trimming is strongly needed.

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

Completeness3/5

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

For a two-optional-parameter list tool with no output schema, the description does explain the returned shape (address/value pairs) and the metadata layers. However, it omits whether the address and document parameters filter or scope results, and gives no sense of result volume, which matters for a tool promising 'every' symbol.

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 description coverage is 100%, so the schema already documents both the address format (0x-prefixed hex, provider-normalized) and the document/target switching via open_binary. The description adds nothing about how those parameters affect the listing — notably it never says whether supplying an address narrows the result despite claiming to list 'every' symbol — so it sits at the baseline 3.

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 memory and external symbol as address/value pairs', which tells an agent exactly what comes back. It does not explicitly distinguish itself from sibling listers such as list_segments, list_strings, or list_procedures, nor from the mutation counterpart set_addresses_names, so it falls short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no named alternatives. The agent must infer from the verb that this is the enumeration path for symbols, and must guess on its own when to prefer list_segments or address_name instead.

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