Skip to main content
Glama

Set Addresses Names

set_addresses_names
DestructiveIdempotent

Assign analyst names to multiple mapped addresses in one call, validating destinations and unique labels, then return per-address edit and readback success booleans.

Instructions

Assign analyst names to multiple mapped addresses in one call and return per-address edit/readback success booleans. Hopper validates mapped destinations, native string representations, its 1024 UTF-16 code-unit symbol-name limit, and unique destinations/names before applying edits. Existing labels may move or swap only among explicitly selected addresses; unselected label owners remain unchanged. This mutates analysis metadata; verify failures individually.

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": {
      "names": {
        "0x1000": "entry"
      }
    },
    "name": "set_addresses_names"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesYes
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
Behavior4/5

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

Annotations already declare destructive=true and idempotent=true, but the description adds real value beyond them: pre-apply validation of mapped destinations, uniqueness of destinations/names, the 1024 UTF-16 code-unit limit, the rule that existing labels may move or swap only among selected addresses while unselected owners stay unchanged, and a per-address boolean return shape. It stops short of explaining permission requirements or how to remediate a failed address.

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 action and result shape, then validation and mutation caveats. Dense but each sentence carries distinct information; minor jargon ('native string representations', 'Hopper validates') adds slight reading cost.

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 destructive batch mutation with no output schema, the description supplies what an agent needs: return shape (per-address success booleans), validation constraints, and the scope of label movement. Missing only auth/permission expectations and any guidance on resolving an individual failure beyond 'verify failures individually'.

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 50% and the `names` property has no inline description, so the description must carry it. It does so reasonably: the map keys are mapped addresses and the values are analyst names, subject to native string representation and a 1024 UTF-16 code-unit limit. It could be more explicit about accepted key formats (the schema example uses '0x1000').

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 specific verb+resource: 'Assign analyst names to multiple mapped addresses in one call.' The word 'multiple' implicitly separates it from the singular sibling set_address_name, though it never names that sibling directly.

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?

Batch usage is implied ('in one call', 'multiple mapped addresses') and the closing 'verify failures individually' hints at partial-success follow-up, but there is no explicit statement of when to prefer this over set_address_name or to cross-check with list_names. Guidance is inferable rather than stated.

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