Skip to main content
Glama

List Bookmarks

list_bookmarks
Idempotent

Lists every bookmark in the selected Hopper document as address and name pairs, keeping null names for unnamed entries for analyst navigation; it does not find code references.

Instructions

List every bookmark in the selected Hopper document as address and name pairs; unnamed bookmarks retain a null name. Use bookmarks as analyst-authored navigation aids; this does not discover code references.

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

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

A4.3/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the result shape (address/name pairs) and the null-name edge case for unnamed bookmarks, which an agent cannot learn from readOnlyHint/destructiveHint/idempotentHint. The one tension is that annotations set readOnlyHint=false while the text describes a pure listing operation, but the description never asserts a read-only guarantee, so this is an inconsistency in the annotations rather than a contradiction of them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler, with the scope and output shape front-loaded and the exclusion last. Every clause earns its place.

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

Completeness5/5

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

For a one-parameter listing tool with no output schema, the description covers scope, return shape, and the null edge case. Nothing an agent needs to call it correctly or interpret its results is missing.

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% and the single parameter is already documented as the active target's document, so the schema does the heavy lifting. "In the selected Hopper document" reinforces that framing but adds no syntax, default, or switching detail; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"List every bookmark in the selected Hopper document as address and name pairs" gives a specific verb, resource, scope and output shape. The follow-up clause rules out the most likely misreading (code references), so an agent can separate this from reference-oriented siblings without opening a schema.

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

Usage Guidelines4/5

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

It supplies real usage framing -- bookmarks are analyst-authored navigation aids -- and an explicit exclusion: this does not discover code references. What is missing is a named alternative for the code-reference case, which keeps it short of a 5.

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