Skip to main content
Glama

Set Address Name

set_address_name
DestructiveIdempotent

Assign an analyst name to a mapped hexadecimal address and verify the metadata edit with an exact readback match. Use the multi-address tool to move or swap labels owned by another address.

Instructions

Assign an analyst name to one mapped hexadecimal address and report whether the native edit succeeded and exact readback matched. Hopper rejects symbol names exceeding 1024 UTF-16 code units before mutation, and rejects names owned by another address; use set_addresses_names to explicitly move or swap labels among selected addresses. This mutates analysis metadata.

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": "entry",
      "address": "0x1000"
    },
    "name": "set_address_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesExact name used by this operation.
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

A4.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important pre-mutation validation rules, rejection conditions, readback behavior, and the fact that analysis metadata is mutated. This adds material behavioral context rather than repeating readOnly, destructive, or idempotent hints.

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?

The description is front-loaded with the core action, followed by constraints, the alternative tool, and the mutation warning. Every sentence carries useful information and there is no redundant restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with three parameters, full schema coverage, and no output schema, the description provides the missing operational context: success/readback reporting, validation limits, ownership rejection, alternative behavior, and mutation disclosure. An agent has enough information to call it correctly.

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 adds meaningful constraints on the name parameter and clarifies that the address must be a single mapped hexadecimal address. The document parameter remains documented only by the schema, so it does not fully earn a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: assign an analyst name to one mapped hexadecimal address. It also explicitly contrasts the single-address behavior with set_addresses_names, so the agent can distinguish the two tools without opening schemas.

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?

It names the alternative tool and the condition that selects it: use set_addresses_names to move or swap labels among selected addresses. It also gives concrete rejection cases, including name length and ownership by another address, which help the agent avoid failed calls.

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