Skip to main content
Glama

Nansen Smart Money Holdings

nansen_smart_money_holdings
Read-onlyIdempotent

What does smart money hold on chain X, returns tokens currently held by Nansen "Smart Money" wallets on a chain, ranked by USD value held, with holder counts and 24h balance change. Example: nansen_smart_money_holdings({ chain: "ethereum", _apiKey: "your-nansen-key" })

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": {
      "chain": "ethereum",
      "_apiKey": "your-nansen-api-key"
    },
    "name": "nansen_smart_money_holdings"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoChain to query (default "ethereum"), e.g. "ethereum", "solana", "base", "arbitrum".
limitNoMax tokens to return (default 20, max 50).
_apiKeyYesNansen API key from your nansen.ai account (paid, $10/10k credits PAYG).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"Nansen API key from your nansen.ai account (paid — $10/10k credits PAYG)."New value: +"Nansen API key from your nansen.ai account (paid, $10/10k credits PAYG)."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds value beyond that by disclosing the result shape (ranked by USD value, holder counts, 24h balance change) in the absence of an output schema, plus the default chain. It omits pagination behavior and any note on credit consumption, which the schema only hints at via the API-key field.

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 key content — what is returned and how it is ranked — is front-loaded, and the example call is a compact illustration. The opening is a slightly awkward run-on ('What does smart money hold on chain X, returns tokens...'), which costs a point but does not obscure meaning.

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 read-only, three-parameter tool with no output schema, the description does the important extra work of enumerating the returned fields and their ordering. Only minor gaps remain (pagination/limit interaction, credit cost), and those are largely handled by 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%, so chain, limit (default 20, max 50) and _apiKey are already documented in the schema. The description adds only a concrete example invocation, which duplicates the schema's examples block. Baseline 3 applies when the schema does the heavy lifting.

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 uses a specific verb and resource: it returns tokens currently held by Nansen 'Smart Money' wallets on a chain, ranked by USD value, with holder counts and 24h balance change. That is far more concrete than a restated name. It does not, however, explicitly contrast itself with the sibling nansen_smart_money_netflow, so an agent must infer the holdings-vs-flows distinction.

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 framing 'What does smart money hold on chain X' implies the use case (portfolio/snapshot questions) but never states when to prefer this over netflow or wallet profiler tools, nor any prerequisites. Usage is implied rather than prescribed.

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.