Skip to main content
Glama

EmblemAI AgentWallet

nansen: nansen_fund_holdings

nansen_fund_holdings
Read-onlyIdempotent

Tokens held by crypto funds / VCs (Nansen Fund label), aggregated like Smart Money holdings. Funds are NOT part of Smart Money, so use this for 'what are funds/VCs holding'. Beta endpoint. 5 credits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nansen_fund_holdings"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for pagination (default 1)
limitNoRows to return (1-100, default 20)
chainsNoChains to query (default: ethereum, solana and robinhood)
sectorsNoExact, case-sensitive token sector names (e.g. 'DeFi', 'Memecoins', 'AI'). Call nansen_token_sectors for the full list.
sort_byNo
sort_directionNoSort direction (default DESC)
max_market_cap_usdNo
min_market_cap_usdNo
include_stablecoinsNo
include_native_tokensNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Adds real context beyond the annotations: the label definition, the aggregation model (like Smart Money holdings), beta status (stability caveat), and a concrete cost of 5 credits. Annotations already cover read-only/idempotent/non-destructive, so the remaining gap is return shape and pagination behavior.

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?

Three tight sentences, front-loaded with what the tool returns, then routing, then operational facts. No filler; the short fragments ('Beta endpoint. 5 credits.') carry information efficiently.

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?

For a 10-parameter, no-output-schema tool, the definition covers purpose, cost, and differentiation but leaves an agent guessing at return fields and at how the filters interact. Adequate to select the tool, insufficient to invoke it precisely without reading the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Ten parameters with only 50% schema description coverage, and the description contributes nothing about any of them — not the cost/volume tradeoff of limit, not the semantics of the USD-value and market-cap filters, not whether stablecoin/native-token flags default on. Half the schema's parameters are undocumented in both places.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Tokens held by crypto funds / VCs'), pins the label it derives from (Nansen Fund), and explicitly contrasts with Smart Money holdings — so an agent can distinguish it from nansen_smart_money_holdings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit selection rule: funds are NOT part of Smart Money, so use this tool for 'what are funds/VCs holding'. That is clear routing guidance, though it never names the sibling tool nor states an exclusion case where this tool should be avoided.

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