Skip to main content
Glama

List Segments

list_segments
Idempotent

Retrieve memory segments or blocks using exclusive end addresses and report permissions, address space, image base, initialization, and overlay facts for the active target.

Instructions

List segments or memory blocks using exclusive end addresses. Ghidra reports block permissions, address space, image base, initialization, and overlay facts; Hopper marks unavailable permissions explicitly.

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

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
Behavior4/5

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

Annotations only declare the safety profile (non-destructive, idempotent, closed-world), and the description adds genuinely new context about what the results contain: Ghidra reports block permissions, address space, image base, initialization, and overlay facts, while Hopper marks unavailable permissions explicitly. That provider-difference disclosure is exactly the kind of behavior an agent cannot get from the structured fields.

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 the core action front-loaded and the provider-specific return details following. No filler, though the second sentence packs several comma-separated facts that could be easier to scan as a short list.

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 carries the burden of explaining return content, and it does so at a useful level by naming the specific fields each provider surfaces. For a one-optional-parameter read tool, that is close to complete, with only the per-provider field set for non-Ghidra/Hopper targets 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?

There is a single optional 'document' parameter and schema description coverage is 100%, so the schema already explains that it selects the active target's provider document. The description adds nothing about that parameter, so the baseline 3 applies under the high-coverage rule.

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 opens with a concrete verb and resource: 'List segments or memory blocks,' which immediately tells an agent what data comes back. It adds a distinguishing detail ('exclusive end addresses') that separates it from other listing tools, though it never names a specific sibling or scoping boundary.

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 exclusions, and no pointer to an alternative (e.g., binary_overview or list_documents) when the agent wants higher-level layout information. The only usage-adjacent content is the note that end addresses are exclusive, which is a data-semantics hint rather than selection 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