Skip to main content
Glama

EmblemAI AgentWallet

nansen: nansen_token_holders

nansen_token_holders
Read-onlyIdempotent

Top holders of a token with labels, balance, USD value, ownership %, and 24h/7d/30d balance changes. Filter to Smart Money, whales, public figures or exchanges. 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": {
      "chain": "<chain>",
      "token_address": "<token_address>"
    },
    "name": "nansen_token_holders"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for pagination (default 1)
chainYes
limitNoRows to return (1-100, default 20)
sort_byNoSort field (default value_usd)
label_typeNoHolder group (default all_holders)
token_addressYesToken contract address (use nansen_search to resolve a symbol first)
include_labelsNoOnly include wallets carrying at least one of these labels
sort_directionNoSort direction (default DESC)
aggregate_by_entityNoGroup wallets by entity (default false; not allowed with smart_money)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world behavior, so the bar is lower. The description still adds a genuinely non-structured trait: the cost ('5 credits'), which an agent cannot derive from annotations or schema. It stops short of noting pagination caps or result volume, but the added cost signal is real value.

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?

Three short clauses, front-loaded with what is returned, then how to filter, then cost. No filler, no restatement of the title, and the credit price is placed last where it is easy to scan.

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 9 parameters, no output schema, and rich annotations, the description fills the important gaps by enumerating return fields so the agent knows what comes back. It could mention large-result handling or that token_address must first be resolved via nansen_search, but that hint already lives in 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 89%, so the schema carries the parameter burden and baseline 3 applies. The description's filter sentence loosely echoes the label_type/include_labels enums without adding syntax, defaults, or constraints (e.g. that aggregate_by_entity conflicts with smart_money, which only the schema states).

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 resource and scope ('Top holders of a token') and enumerates the payload fields: labels, balance, USD value, ownership %, and 24h/7d/30d balance changes. It is clearly distinguishable from flow/transfer siblings by name alone, though it never explicitly names an alternative.

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?

'Filter to Smart Money, whales, public figures or exchanges' describes how to narrow results but not when to pick this tool over nansen_token_flows, nansen_token_transfers, or nansen_smart_money_holdings. Usage is implied (holder-distribution analysis) rather than stated, and no exclusions are given.

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