Skip to main content
Glama

Address Name

address_name
Idempotent

Resolve the primary analyzed name at a code or data address, using an explicit address for headless providers or the current cursor for GUI providers.

Instructions

Resolve the primary analyzed name at a code or data address. Headless providers require an explicit address; GUI providers may default to their current cursor. Null means the provider has no primary name at that address.

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

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.9/5.0
Behavior4/5

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

Annotations cover safety (non-destructive, idempotent) but the description adds information annotations cannot: provider-dependent defaulting of the address and the meaning of a null result (provider has no primary name). It does not explain why readOnlyHint is false for what reads like a lookup, which would have clarified whether resolution triggers analysis.

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?

Three short sentences, each carrying distinct information: the action, the provider-mode prerequisite, and the null-return semantics. Nothing is repeated from the annotations or schema.

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 lookup with no output schema, the description covers action, parameter prerequisites, and null semantics adequately. The remaining gap is side effects, since readOnlyHint=false hints that resolution may mutate provider state without the description saying so.

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 field-level documentation is already handled, yet the description adds meaning the schema does not: the address parameter is effectively mandatory for headless providers and optional for GUI providers. That changes how an agent decides whether to supply it.

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?

Names a specific verb and resource: "Resolve the primary analyzed name at a code or data address." The read/resolve framing implicitly distinguishes it from the sibling set_address_name, though it never names that counterpart explicitly.

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?

Offers real operational guidance about provider modes (headless requires an explicit address, GUI may default to the cursor), which is genuinely useful context. However, it never states when to prefer this over siblings such as current_address, inspect_address_context, or set_address_name, so tool selection is left to inference.

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