Skip to main content
Glama

Prev Address

prev_address
Idempotent

Navigate to the previous analyzed object start before an address or current cursor, enabling backward traversal of analyzed code or memory. May fail at document boundaries.

Instructions

Return the previous analyzed object start before an explicit address or current cursor. This is a navigation primitive and may fail at document boundaries; data objects and instructions remain distinct from control flow.

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": "prev_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.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false, idempotentHint=true and openWorldHint=false, so the bar is lowered; the description still contributes the useful caveat that the call may fail at document boundaries. However, it never explains that readOnlyHint=false implies address/cursor state may change, and the closing clause about 'data objects and instructions' versus 'control flow' is opaque rather than informative.

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

Conciseness4/5

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

Purpose is front-loaded in the first sentence and there is no padding. The second sentence mixes a valuable caveat with a cryptic clause that costs more attention than it returns.

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-parameter navigation primitive with no output schema and full schema coverage, the definition covers the important unknowns: the default-cursor behavior and the possibility of failure at boundaries. It stops short of describing what 'previous analyzed object' concretely yields, which would fully close the gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description genuinely adds semantics the schema lacks: it clarifies that address is optional and that omitting it operates on the current cursor. The document parameter's role in target switching is left entirely to the schema.

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 action ('Return the previous analyzed object start') plus the two anchoring modes (explicit address or current cursor). The phrase 'analyzed object start' is domain jargon that is never unpacked, and the implicit counterpart next_address is not named, so differentiation from siblings relies on the word 'previous' alone.

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?

Usage is only implied: the agent must infer that this is cursor-stepping navigation and that omitting address falls back to the current cursor. There is no explicit statement of when to prefer this over next_address, goto_address, or current_address, and no prerequisites, though the boundary-failure caveat does hint at when it will not work.

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