Skip to main content
Glama

Unset Bookmark

unset_bookmark
DestructiveIdempotent

Remove a bookmark at a specified hexadecimal address and report whether it is absent; updates navigation metadata only, leaving binary bytes unchanged.

Instructions

Remove the bookmark at a mapped hexadecimal address and return whether it is absent. Hopper also permits removing an existing legacy bookmark outside mapped memory. This mutates navigation metadata and does not alter binary bytes.

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": {
      "address": "0x1000"
    },
    "name": "unset_bookmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesA 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.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the mutation profile is known. The description does add genuine value by clarifying that only navigation metadata is mutated and binary bytes are untouched, plus that the result reports absence — context the annotations cannot convey. It says nothing about failure modes (e.g. removing a nonexistent bookmark) or permission requirements.

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

Conciseness3/5

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

Three short sentences with no filler, and the core operation is front-loaded. It is close to minimal, though the legacy-bookmark sentence sits slightly awkwardly between the action and the metadata caveat.

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?

For a simple two-parameter mutation with full schema coverage and complete annotations, the description covers the action, the return meaning, and the scope caveat, so an agent has what it needs. Only error behavior on a missing bookmark is left unaddressed.

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 coverage is 100%, so both address and document semantics come from the schema itself. The description reinforces the hexadecimal address expectation and the mapped-memory constraint but adds no syntax or format detail beyond that, and it never mentions the document parameter.

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 names a specific verb and resource ('Remove the bookmark') and scopes it to a 'mapped hexadecimal address', which cleanly separates it from the set_bookmark counterpart. It never names the sibling explicitly, so the differentiation is implicit rather than stated.

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?

The reader can infer when to use it (removing an existing bookmark), and one edge case is called out: legacy bookmarks outside mapped memory are also removable. There is no explicit when-to-use/when-not guidance, no prerequisites, and no reference to set_bookmark as the inverse operation.

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