Skip to main content
Glama

Set Bookmark

set_bookmark
DestructiveIdempotent

Create or replace an analyst-authored navigation bookmark at a mapped hexadecimal address and report success, without modifying binary evidence.

Instructions

Create or replace a bookmark at a mapped hexadecimal address and report success. This mutates navigation metadata; bookmarks are analyst-authored navigation aids, not binary evidence.

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": "set_bookmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoExact name used by this operation.
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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=true, and the description meaningfully sharpens that: 'create or replace' explains the idempotent overwrite behavior, and the note that bookmarks are analyst-authored navigation aids rather than binary evidence scopes what 'destructive' actually touches. It does not describe error behavior for unmapped addresses, but the added context beyond annotations is real.

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, front-loaded with the action and target, with the second sentence carrying genuinely useful scope information rather than filler. Nothing is redundant.

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 3-parameter mutation tool with no output schema, the definition covers what it does, that it reports success, and that only navigation metadata changes. Minor gaps remain around failure modes for unmapped addresses and what the reported success contains.

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 address, name, and document, so the baseline is 3. The description adds only the 'mapped hexadecimal' qualifier for address and says nothing about name matching or the document parameter, which the schema already covers via a pointer to open_binary.

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 pair (create or replace) and resource (bookmark) at a mapped hexadecimal address, which is far more precise than the title alone. It is implicitly distinguishable from unset_bookmark, but it never names a sibling or explicitly contrasts create-with-replace semantics with removal.

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 phrase 'at a mapped hexadecimal address' implies a precondition (the address must already be mapped), which is useful implied guidance. However, there is no explicit when-to-use/when-not-to-use statement and no pointer to unset_bookmark for removal, so the agent must infer the boundaries.

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