Skip to main content
Glama

Searching tokens, companies, and addresses

general_search
Read-onlyIdempotent

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

    • 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

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": "general_search"
  }
}

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" ("all" is the same as "any")any

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / result_type / description
      Previous value: -"Type filter - \"token\", \"entity\", \"wallet\", \"eoa\", \"stock\", or \"any\""New value: +"Type filter - \"token\", \"entity\", \"wallet\", \"eoa\", \"stock\", or \"any\" (\"all\" is the same as \"any\")"
    • changedInput schema / properties / result_type / enum
      Previous value: -[
      -  "token",
      -  "entity",
      -  "wallet",
      -  "eoa",
      -  "stock",
      -  "any"
      -]New value: +[
      +  "token",
      +  "entity",
      +  "wallet",
      +  "eoa",
      +  "stock",
      +  "any",
      +  "all"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / result_type / description
      Previous value: -"Type filter - \"token\", \"entity\", \"wallet\", \"eoa\", \"stock\", \"trader\", 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",
      -  "stock",
      -  "trader",
      -  "any"
      -]New value: +[
      +  "token",
      +  "entity",
      +  "wallet",
      +  "eoa",
      +  "stock",
      +  "any"
      +]
  3. Changed2 schema fields changed
    • changedInput schema / properties / result_type / description
      Previous value: -"Type filter - \"token\", \"entity\", \"wallet\", \"eoa\", \"stock\", or \"any\""New value: +"Type filter - \"token\", \"entity\", \"wallet\", \"eoa\", \"stock\", \"trader\", or \"any\""
    • changedInput schema / properties / result_type / enum
      Previous value: -[
      -  "token",
      -  "entity",
      -  "wallet",
      -  "eoa",
      -  "stock",
      -  "any"
      -]New value: +[
      +  "token",
      +  "entity",
      +  "wallet",
      +  "eoa",
      +  "stock",
      +  "trader",
      +  "any"
      +]
  4. 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"
      +]
  5. 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"
      +]
  6. 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\""
  7. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the description focuses on coverage limits — no NFT support and premium address labels available only on the Nansen research agent — which is genuine context an agent cannot get from annotations. It stops short of describing result shape or ranking behavior, but the presence of an output schema lowers the burden.

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 primary routing statement and the prediction-market exclusion are front-loaded, followed by a scannable capability list. The NFT paragraph is slightly awkward where it sits and the last bullet about the research agent reads like an implementation note, but overall there is little waste.

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 broad, four-parameter, open-world search tool, the description covers what it searches, what it cannot search, what to use instead, and the tier limitation on premium labels. With an output schema present, the omission of return-value detail is acceptable.

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 baseline is 3. The description does add useful meaning about what the query accepts (name, symbol, contract address, domain, entity label), but it never mentions the chain filter, max_results, or the stock result_type, so it does not meaningfully extend 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?

States a specific verb and resource ("look up possible tokens, entities, and addresses") and then enumerates concrete capabilities: token existence checks, entity lookup, label-to-address resolution, and domain resolution. It also names the sibling it is not (prediction_market_lookup), so an agent can route without opening either schema.

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 declares itself the FIRST entry point, then gives a hard exclusion ("Do NOT use this tool for prediction markets") with the correct alternative and the trigger conditions (Polymarket names, topics, event slugs, URLs). It also handles the NFT edge case by instructing the agent to still probe via this tool when a name might collide with a fungible token.

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