Skip to main content
Glama

Goto Address

goto_address
Idempotent

Move Hopper's GUI cursor to a mapped address and return the observed cursor address. Unmapped destinations fail without moving the cursor; changes navigation state only.

Instructions

Move Hopper's GUI cursor to a mapped address and return the observed cursor address. Interior coordinates snap to the containing analyzed object's start. Unmapped destinations fail without moving the cursor. This changes navigation state but not analysis data; use explicit-address tools for headless workflows.

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

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

A4.5/5.0
Behavior5/5

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

Annotations only declare a non-read-only, non-destructive, idempotent local mutation; the description goes well beyond by disclosing the return value, the snapping rule for interior coordinates, the failure mode for unmapped destinations ('fail without moving the cursor'), and the exact side effect ('changes navigation state but not analysis data'). That is precisely the extra context an agent needs before invoking a state-changing tool.

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?

Four short sentences, front-loaded with the action, followed by edge-case behavior and then the alternative-tool routing. No filler and no repetition of annotation facts.

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?

Despite having no output schema, the description names what is returned, how coordinates are normalized, what happens on failure, and what state it does and does not touch. Nothing material is missing for a two-parameter navigation tool.

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 address format and the document parameter are already documented in structured fields. The description adds nothing about either parameter, which is acceptable at high coverage but yields only the baseline.

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?

States a specific verb and resource ('Move Hopper's GUI cursor to a mapped address') plus the return value ('return the observed cursor address'), and separates itself from the explicit-address tool family. An agent can tell this is GUI navigation, not analysis, immediately.

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?

Gives an explicit when-not: 'use explicit-address tools for headless workflows' is the alternative for non-GUI cases. No named sibling is given and there is no guidance on prerequisites such as having a target open, but the routing condition is clear.

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