Skip to main content
Glama

Next Address

next_address
Idempotent

Return the next analyzed object address after a specified address or current cursor to navigate analyzed objects in a binary document.

Instructions

Return the next analyzed object address after an explicit address or current cursor. This is a navigation primitive, not instruction-flow or CFG analysis.

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

Input Schema

NameRequiredDescriptionDefault
addressNoA 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
Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, so a 3 is the appropriate bar. The description adds one genuinely useful trait beyond them: it only returns *analyzed* object addresses, implying unanalyzed regions may be skipped. It says nothing about what happens when no further address exists (end-of-space behavior) or why readOnlyHint is false for a call that appears to only read.

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 short sentences with the core behavior front-loaded and the scope exclusion second. Nothing is repeated and nothing is padding.

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 two-optional-parameter navigation primitive with full schema coverage and no output schema, the description covers the essential contract: what is returned, where iteration starts, and what the tool is not. Only the end-of-iteration/termination condition and the cursor state interaction are left implicit.

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 the schema already documents both parameters, which sets the baseline at 3. The description does add a little meaning the schema does not: the address argument behaves as an optional starting point and omitting it falls back to the current cursor, and the term "analyzed object address" narrows what counts as a valid next value.

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 the next analyzed object address") and scopes it to an explicit address or the current cursor. The second sentence carves it away from instruction-flow/CFG analysis, though it never names the obvious sibling prev_address, so an agent must infer the pairing.

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?

The clause "after an explicit address or current cursor" makes clear it is for stepping through addresses starting from either a supplied value or the session cursor. "Navigation primitive, not instruction-flow or CFG analysis" is a useful negative guideline steering agents away from expecting disassembly-level results, but there is no explicit mention of when goto_address or prev_address should be preferred.

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