Skip to main content
Glama

Current Address

current_address
Idempotent

Returns Hopper's current cursor address for the selected document to support interactive navigation state; use explicit addresses instead for reproducible investigations.

Instructions

Return Hopper's current cursor address for the selected document. Use only for interactive navigation state; prefer explicit addresses in reproducible investigations.

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

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

A3.9/5.0
Behavior3/5

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

Annotations declare idempotent, non-destructive, non-open-world but readOnlyHint=false, and the description's 'Return ...' framing gives no hint of any side effect or why the tool is not marked read-only. It adds useful scoping context (per-document cursor, interactive-only) but leaves the state-mutation question unresolved rather than contradicting it outright.

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, zero filler, with the core behavior front-loaded and the restriction trailing as a qualifier. Nothing could be removed without losing the usage constraint.

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?

For a simple single-parameter tool this is nearly sufficient, but with no output schema the description never says what the returned address looks like (hex string, object, provider-qualified name) or what happens when no cursor is set. That return-shape gap is the main missing piece.

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?

Only one optional parameter, fully described in the schema (100% coverage) as the active target's provider document name. The description's 'selected document' phrasing mirrors that semantic but adds no new detail on defaults or how the active target is chosen; baseline 3 applies.

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 and resource: 'Return Hopper's current cursor address for the selected document.' An agent can distinguish it from the inspection siblings (current_document, current_procedure, goto_address) by the 'cursor address' resource and the 'selected document' scope, though it never names the nearest alternatives explicitly.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use ('interactive navigation state') and an explicit when-to-prefer-something-else ('prefer explicit addresses in reproducible investigations'), which is the exact routing decision an agent needs.

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