Skip to main content
Glama

Looking up address labels

address_labels
Read-onlyIdempotent

Get the standard labels for one wallet address.

This tool returns identity, behavioural, and protocol labels. It does not return premium labels.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "request": "<request>"
    },
    "name": "address_labels"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYesRequest for the standard labels of one wallet address.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / request / properties / chain / enum
      Previous value: -[
      -  "all",
      -  "arbitrum",
      -  "avalanche",
      -  "base",
      -  "bnb",
      -  "ethereum",
      -  "hyperevm",
      -  "hyperliquid",
      -  "iotaevm",
      -  "linea",
      -  "mantle",
      -  "monad",
      -  "optimism",
      -  "plasma",
      -  "polygon",
      -  "robinhood",
      -  "sei",
      -  "solana",
      -  "sonic",
      -  "tron"
      -]New value: +[
      +  "all",
      +  "arbitrum",
      +  "arc",
      +  "avalanche",
      +  "base",
      +  "bnb",
      +  "ethereum",
      +  "hyperevm",
      +  "hyperliquid",
      +  "iotaevm",
      +  "linea",
      +  "mantle",
      +  "monad",
      +  "optimism",
      +  "plasma",
      +  "polygon",
      +  "robinhood",
      +  "sei",
      +  "solana",
      +  "sonic",
      +  "tron"
      +]
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorld, so safety behavior is covered. The description still adds genuine value beyond them by disclosing the label categories returned and the premium-label exclusion, which is a real result-set boundary. It says nothing about completeness of coverage across chains or how sparse results may be, so it is a modest addition rather than rich behavioral context.

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?

Two short sentences with the core action front-loaded and the scope limitation immediately following; there is no redundant wording. Slightly tight against a 5 only because the second sentence could have been framed as routing guidance instead of a bare negative.

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 an output schema present, return-shape explanation is unnecessary, and the single nested request object is fully documented in the schema with rich annotations. The description covers the essential scope question (standard vs premium labels) that the structured fields do not express. Minor omission is any note on default chain='all' breadth or result sparsity, which matters for interpretation but is inferable from the schema.

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%, including descriptions for address, chain, page, and perPage, so the schema carries parameter meaning. The description only reinforces that the target is a single wallet address and adds nothing on chain scoping or pagination semantics. Baseline 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 states a specific verb and resource ('Get the standard labels for one wallet address') and further qualifies the result set as identity, behavioural, and protocol labels, which lets an agent tell it apart from a general search tool. It stops short of naming any sibling tool or contrasting with a premium-label lookup, so differentiation is by scope only.

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?

There is an implied when-not: 'It does not return premium labels' tells the agent this tool is the wrong choice for premium label needs. However, no alternative is named for that case, and there is no guidance on when this should be preferred over the many address-oriented siblings such as entity_name_search.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources