Skip to main content
Glama

Address To File Offset

address_to_file_offset
Idempotent

Map a provider-normalized address to its original file offset, validate bytes against the executable digest, and translate FAT image-relative offsets; unmapped or changed sources return typed errors.

Instructions

Map one provider-normalized virtual address to its original nonnegative file offset. Hopper verifies the original bytes against the selected executable digest and translates FAT image-relative offsets using the loaded header. Results preserve the provider coordinate, image base, and source path. Unmapped addresses fail explicitly; changed or unavailable sources return typed errors retaining native mapping facts as partial 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": "address_to_file_offset"
  }
}

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

A3.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses substantive behavior: digest verification of the original bytes, FAT image-relative offset translation via the loaded header, which facts are carried into results (provider coordinate, image base, source path), and explicit failure semantics including typed errors that retain native mapping facts as partial evidence. Annotations only say idempotent, non-destructive, closed-world, so this description adds real information rather than restating it.

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?

Four sentences, front-loaded with the core mapping statement, then verification, then result shape, then failure modes. Every sentence carries content, though the density of provider/header/digest jargon is slightly heavy for a two-parameter tool.

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?

With no output schema and only two parameters, the description does well: it describes what results carry and how failures are reported. The only gap is how an agent should establish or confirm the active provider document before calling, which is left entirely to the schema's document field.

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 both parameters (address, document) are already documented, including the 0x-hex convention and how to switch targets via open_binary. The description reinforces that a single provider-normalized address is expected but adds no syntax or format detail beyond the schema, so the baseline of 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?

The description opens with a precise verb and resource: 'Map one provider-normalized virtual address to its original nonnegative file offset.' That is unambiguous and clearly a translation/query operation. It does not name or contrast with any sibling (e.g., inspect_address_context or address_name), so it stops short of the sibling differentiation required for a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative. The word 'one' weakly implies single-address versus batch use, and 'provider-normalized' hints at the input contract, but an agent gets no help deciding between this tool and the other address-oriented siblings.

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