anchain-data-mcp

Official

Overview Schema Source Related Servers Discussions Admin

get_address_label

Retrieve the category label and associated entity for any blockchain address across major protocols. Supports BTC, ETH, and more for risk assessment and compliance checks.

Instructions

Retrieve the category label for a blockchain address, including the associated entity when available.

Args: proto: Blockchain protocol (btc, eth, xlm, xmr, bnb, matic, avax, sol, trx, ada, dot, ltc, bch, algo, xrp) address: Blockchain address to query (e.g. 0x2f389ce8bd8ff92de3402ffce4691d17fc4f6535)

Cost: 5 credits

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": {
      "proto": "<proto>",
      "address": "<address>"
    },
    "name": "get_address_label"
  }
}

Input Schema

Name	Required	Description	Default
`proto`	Yes
`address`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 1, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the burden. It discloses cost (5 credits) and conditionality ('when available'), but fails to mention error handling, rate limits, or data freshness. With zero annotation coverage, this is insufficient for a fully transparent operation.

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?

The description is concise, with a one-sentence purpose, a structured Args block, and a cost note. Each element serves a purpose, though the protocol list is lengthy and could be moved to an enum in the schema to reduce verbosity.

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

Completeness3/5

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

The output schema exists, so return values need no elaboration. However, the description lacks guidance on when to use this single-address tool versus bulk operations, and omits any behavioral caveats beyond cost. For a simple lookup with good parameter hints, it is barely adequate but not fully complete.

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 description coverage is 0%, but the description's Args section compensates by listing valid protocols (btc, eth, etc.) and providing an example address. This adds significant meaning beyond the bare schema types, though it could further explain address format per protocol.

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 clearly states the tool retrieves a category label for a blockchain address and includes associated entity when available. This distinguishes it from siblings like get_address_risk_score or bulk_address_label, though it does not explicitly name them. The verb 'retrieve' and resource 'category label' are specific.

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?

Usage context is implied by the tool's purpose and sibling names, such as bulk_address_label for batch operations and get_address_risk_score for risk scoring. However, there is no explicit when-to-use or alternative mention, leaving selection to inference.

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