Skip to main content
Glama

List Documents

list_documents
Idempotent

Lists provider program or document identities, showing whether Hopper exposes multiple documents or a Ghidra headless session contains one imported Program.

Instructions

List provider program or document identities. Hopper may expose several documents; a Ghidra headless session contains exactly its one imported Program.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false, openWorldHint=false, idempotentHint=true and destructiveHint=false, yet the description frames the tool purely as a passive "List" with no hint of why it is not considered read-only (e.g., attaching to or spawning a provider). It also says nothing about cost, latency, or ordering of results. With annotations present the bar is lower, but this description adds only cardinality context and leaves the non-read-only flag unexplained.

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 short sentences, front-loaded with the verb and resource, then a useful elaboration on what to expect per backend. No filler, though "provider program or document identities" could be stated more plainly.

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?

With no output schema, the description should say what a returned "document identity" actually looks like (name, id, provider association) and whether the result is empty when no provider is connected. The per-backend cardinality note is genuinely helpful, but the return shape and the not-read-only behavior remain undisclosed for a tool whose whole job is producing a list.

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

Parameters4/5

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

The tool takes zero parameters and the description correctly spends no words on inputs. Baseline for a no-parameter tool is a 4; there is nothing it could add here beyond the caveat that no filtering options exist, which it implicitly covers by describing a bare enumeration.

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?

"List provider program or document identities" gives a clear verb (list) and resource (documents/identities), and the second sentence clarifies what a "document" is in two concrete backends (Hopper documents vs. a single Ghidra headless Program). The phrasing "provider program or document identities" is jargon-heavy, and no sibling is named as an alternative, 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?

The description never states when an agent should call this versus other enumeration tools, nor does it mention prerequisites such as being attached to a provider/session first. The cardinality note implies the tool is the entry point for discovering what can be operated on, but that inference is left entirely to the reader.

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