Skip to main content
Glama

Nansen

by io.github.hurcanNansen

Searching onchain data

general_search

General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query.

Do NOT use this tool for prediction markets. For Polymarket names, topics, event slugs, or URLs, use prediction_market_lookup instead.

Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name.

This tool allows you to:

  • Check if a (fungible) token exists by name, symbol, or contract address

  • Search information about a token

    • Current price in USD

    • Trading volume

    • Contract address and chain information

    • Market cap and supply data when available

  • Search information about an entity

  • Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNoOptional chain filter to narrow down token results to specific blockchain. If not further specified, leave it as None. If a chain is specified, ALWAYS use this parameter instead of adding chain name to the query string. Valid values: "ethereum", "solana", "base", "bnb", "polygon", "arbitrum", "avalanche", "optimism", etc.
queryYesThe search term - token symbol, name, or address. DO NOT include chain name here!
max_resultsNoMaximum number of results (default: 25, max: 25)
result_typeNoType filter - "token", "entity", "eoa", or "any"any

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses key behavioral traits: no NFT support, ability to search by name/symbol/address, returned data types (price, volume, contract, chain, market cap, supply), and domain resolution. It does not mention rate limits or pagination, but it covers the most important limitations and capabilities.

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 well-organized with a clear opening statement, concise exclusions, and a bulleted list of capabilities. It is somewhat lengthy but every sentence serves a purpose, and the front-loaded 'FIRST entry point' immediately orients the agent.

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

Completeness5/5

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

The tool is a general search with 4 parameters and an output schema, so return values are covered by the schema. The description thoroughly covers when to use it, what it can/cannot do, and key parameter constraints. It is sufficient for an agent to select and invoke this tool correctly in most scenarios.

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 coverage is 100%, so baseline is 3. The description adds critical cross-parameter guidance: 'DO NOT include chain name here' for query and 'ALWAYS use this parameter instead of adding chain name to the query string' for chain. This goes beyond the schema and prevents common invocation errors.

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?

Description clearly states the tool is a general search entry point for tokens, entities, and addresses, with specific verbs like 'look up' and 'search'. It explicitly distinguishes itself from sibling tools by excluding prediction markets and NFTs, and names the alternative tool for prediction markets.

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

Usage Guidelines5/5

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

Explicitly identifies itself as the 'FIRST entry point' for lookups, provides a clear exclusion ('Do NOT use this tool for prediction markets'), and points to a specific alternative (`prediction_market_lookup`). Also advises checking token queries even for potential NFTs, giving practical when-to-use guidance.

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

All Nansen toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation5/5

Each tool has a clearly defined purpose, and overlapping tools (e.g., token_flows vs token_recent_flows_summary, nansen_score_top_tokens vs token_discovery_screener) include explicit guidance on when to use them. Even with similar names like prediction_market_trades and prediction_market_address_trades, the descriptions and parameters make the distinction unambiguous.

Naming Consistency4/5

Most tools follow a domain_prefix_noun pattern (address_, token_, prediction_market_), making them predictable within families. However, outliers like general_search, growth_chain_rank, hyperliquid_leaderboard, and transaction_lookup break the pattern, and some names are long or inconsistently formatted (e.g., smart_traders_and_funds_perp_trades vs smart_traders_and_funds_token_balances).

Tool Count3/5

With 38 tools, the server is far above the typical 3-15 range, making it heavy for agents to navigate. However, Nansen is a broad analytics platform covering wallets, tokens, prediction markets, and smart money activity, so the high count is justifiable as each tool serves a distinct function.

Completeness5/5

The tool set provides comprehensive coverage across token analysis (ohlcv, trading, holders, flows, PnL, technicals), wallet analysis (portfolio, transactions, counterparties), prediction markets (lookup, orderbook, trades, PnL), and discovery. The only obvious omission is NFT support, but it is explicitly documented as out of scope, so no critical dead ends exist.

Resources