Skip to main content
Glama

EmblemAI AgentWallet

nansen: nansen_search

nansen_search
Read-onlyIdempotent

Search Nansen for tokens (name/symbol → chain + contract address, price, volume, market cap) and entities (funds, exchanges, public figures). Free. Use it first whenever the user names a token by symbol and you need its address for another Nansen tool.

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": {
      "query": "<query>"
    },
    "name": "nansen_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoOptional chain to narrow token results
limitNo
queryYesToken name/symbol, address or entity name
result_typeNoRestrict results (default any)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered and the description correctly does not re-litigate it. It adds real value with the 'Free' cost signal and by disclosing the shape of token results (address, price, volume, market cap), which matters since there is no output schema. It says nothing about entity result shape, result ranking, or what happens when a symbol is ambiguous across chains.

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?

Two sentences, front-loaded with the verb and resource before the return fields and the calling strategy. Every clause carries information: what it searches, what you get back, that it is free, and when to reach for it. Nothing is redundant with the title.

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 four-parameter lookup tool with no output schema, the description covers input interpretation, return content for tokens, cost, and a usage heuristic, while annotations carry safety. The remaining gap is entity-side behavior and disambiguation, which an agent resolving a bare symbol on a multi-chain tool might reasonably need.

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 75%, so the schema documents most parameters, and the description's 'name/symbol -> chain + contract address' is essentially a restatement of what query resolves to rather than added syntax or format guidance. The chain, result_type and limit parameters receive no mention in the description, though their enum/default semantics are already in the schema. Baseline 3 is the right ceiling here.

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?

States a specific verb and resource ('Search Nansen for tokens ... and entities') and enumerates the payload returned for tokens (chain + contract address, price, volume, market cap). That is far more informative than a restated name. It stops short of explicitly contrasting with the other search siblings (searchCryptoByName, searchEvmTokensBirdeye), leaving the agent to infer which search index to use.

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 concrete routing advice: 'Use it first whenever the user names a token by symbol and you need its address for another Nansen tool.' That establishes a default-first position and the downstream trigger (feeding another Nansen tool). It does not state when NOT to use it or when a sibling search is preferable, so it is clear context without exclusions.

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