Skip to main content
Glama

Nansen

by io.github.nansen-ai
OverviewDiscussionsAdmin

Searching tokens, companies, and addresses

general_search
Read-only

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 the address behind a Nansen label (public figure, fund, exchange wallet)

  • Resolve a domain (.eth, .sol) to its address

  • Look up premium address labels only on the Nansen research agent

Input 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. In stock mode, pass only the company name or exchange ticker. Do not add words such as "stock", "ticker", or a chain name.
max_resultsNoMaximum number of results (default: 25, max: 25)
result_typeNoType filter - "token", "entity", "wallet", "eoa", "stock", or "any"any

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / query / description
      Previous value: -"The search term - token symbol, name, or address. DO NOT include chain name here!"New value: +"The search term - token symbol, name, or address. In stock mode,\n   pass only the company name or exchange ticker. Do not add words\n   such as \"stock\", \"ticker\", or a chain name."
    • changedInput schema / properties / result_type / description
      Previous value: -"Type filter - \"token\", \"entity\", \"wallet\", \"eoa\", or \"any\""New value: +"Type filter - \"token\", \"entity\", \"wallet\", \"eoa\", \"stock\", or \"any\""
    • changedInput schema / properties / result_type / enum
      Previous value: -[
-  "token",
-  "entity",
-  "wallet",
-  "eoa",
-  "any"
-]New value: +[
+  "token",
+  "entity",
+  "wallet",
+  "eoa",
+  "stock",
+  "any"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / result_type / description
      Previous value: -"Type filter - \"token\", \"entity\", \"eoa\", or \"any\""New value: +"Type filter - \"token\", \"entity\", \"wallet\", \"eoa\", or \"any\""
    • changedInput schema / properties / result_type / enum
      Previous value: -[
-  "token",
-  "entity",
-  "eoa",
-  "any"
-]New value: +[
+  "token",
+  "entity",
+  "wallet",
+  "eoa",
+  "any"
+]
  3. Changed5 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / chain / description
      Added value: +"Optional 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.\n   Valid values: \"ethereum\", \"solana\", \"base\", \"bnb\", \"polygon\", \"arbitrum\",\n   \"avalanche\", \"optimism\", etc."
    • addedInput schema / properties / max_results / description
      Added value: +"Maximum number of results (default: 25, max: 25)"
    • addedInput schema / properties / query / description
      Added value: +"The search term - token symbol, name, or address. DO NOT include chain name here!"
    • addedInput schema / properties / result_type / description
      Added value: +"Type filter - \"token\", \"entity\", \"eoa\", or \"any\""
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, non-destructive behavior, and the description adds useful scope and limitation context, especially the NFT support caveat and premium-label restriction. It does not add much about rate limits, pagination, or auth, but the safety profile is already covered by annotations.

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 front-loaded with the primary purpose and exclusion, then uses a readable bullet list for capabilities. It is somewhat verbose, but the structure makes the long capability list scannable and useful for a broad search tool.

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?

Given the tool's breadth, annotations, 100% schema coverage, and presence of an output schema, the description is complete enough for correct selection and invocation. It covers primary use, exclusions, supported query categories, and important domain limitations.

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 the schema already documents all four parameters in detail. The description adds some query-type nuance by mentioning domains and Nansen labels, but for most parameters it does not add meaning beyond the schema.

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?

The description states a specific verb and resource: a general search entry point for tokens, entities, and addresses. It also distinguishes the tool from prediction-market search by naming `prediction_market_lookup` as the sibling for that domain.

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?

It gives explicit routing guidance: use this as the FIRST entry point, do not use it for prediction markets, and use `prediction_market_lookup` for Polymarket names, topics, slugs, or URLs. It also clarifies the NFT limitation while explaining when a token check may still be appropriate.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources