Skip to main content
Glama

EmblemAI AgentWallet

nansen-wallets: nansen_wallet_labels

nansen_wallet_labels
Read-onlyIdempotent

Nansen labels for an address (e.g. Smart Trader, Whale, Fund, exchange or protocol names, bot users). Use to identify who a wallet is. 10 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": {
      "wallet_address": "<wallet_address>"
    },
    "name": "nansen_wallet_labels"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoethereum, solana or robinhood. Default: solana for base58 addresses, ethereum for 0x addresses. For a 0x wallet call again with robinhood to cover Robinhood Chain.
wallet_addressYesWallet address (0x... for Ethereum/Robinhood, base58 for Solana)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive behavior, so the safety profile is covered. The description adds genuinely new context: the 10-credit cost and the kinds of labels returned. It says nothing about whether missing labels yield an empty result or an error, which is the only notable gap.

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, front-loaded with the resource and its label types, with cost appended tersely as '10 credits.' Nothing is padded, though the cost note could be slightly more explicit about units.

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?

A two-parameter read-only tool with full schema coverage, complete annotations, and no output schema to explain. The description covers purpose, label categories, and cost, which is adequate; it could only be stronger by noting what an unlabeled address returns.

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%, and the schema itself documents the chain defaulting logic (base58 to solana, 0x to ethereum) and the robinhood retry hint. The description adds no parameter-level meaning beyond that, so the baseline of 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?

States a specific resource (Nansen labels for an address) and enumerates concrete label categories (Smart Trader, Whale, Fund, exchange/protocol names, bot users), plus the intent 'Use to identify who a wallet is.' That clearly separates it from data siblings like nansen_wallet_pnl or nansen_wallet_balances, though no sibling is named 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?

The phrase 'Use to identify who a wallet is' gives an implied use case, which is enough to orient an agent. It stops short of saying when not to use it or pointing at alternatives such as the profiler for deeper wallet characterization.

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