Skip to main content
Glama

Search token contract addresses across chains by symbol

token_search
Read-only

Finds token contract addresses by symbol or name across chains using DexScreener search and verified lists. Returns matching tokens with chain, contract address, symbol, name, liquidity of largest pool, and verified list membership. Limit up to 25. Information only, not financial advice. Related tools on this server, for a different need: token_metadata when you need token facts read on chain: for an ERC-20 on 22 EVM chains. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "q": "<q>"
    },
    "name": "token_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesToken symbol or name search query (e.g. PEPE, USDC)
chainNoOptional chain filter (e.g. ethereum, solana, base)
limitNoMaximum matching tokens to return (max 25)

Output Schema

NameRequiredDescriptionDefault
countNo
queryNo
sourceNo
tokensNo
checkedAtNo
disclaimerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnly and openWorld, so the description's job is added context — and it delivers: sources searched, a hard result cap of 25, and an explicit cost model ($0.002 per successful call via x402, failed calls not charged). That pricing/payment detail is exactly the kind of behavioral fact not captured in annotations. It stops short of 5 by saying nothing about latency, rate limits, or what an empty result set means.

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?

Purpose, return fields, and the limit are front-loaded in the first three sentences, which is the right order. The tail collapses two unrelated things — sibling routing and pricing — into one long sentence, and the 'not financial advice' disclaimer consumes space for limited routing value.

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?

With an output schema present and full schema coverage, the description needn't enumerate return values, yet it does so briefly and accurately. Payment, sources, and the sibling boundary are all covered. The remaining gap is edge-case behavior — what happens on zero matches or ambiguous symbols like USDC appearing on many chains.

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 coverage is 100%, so all three parameters are already documented with examples (PEPE/USDC, ethereum/solana/base) and the max-25 rule. The description repeats the limit cap and implies the chain filter by 'across chains,' but adds no syntax or format meaning beyond the schema — the correct baseline when the schema does the heavy lifting.

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 first sentence names a specific verb and resource ('Finds token contract addresses by symbol or name across chains') and discloses the data sources (DexScreener search plus verified lists). It explicitly routes a different need to the sibling token_metadata, so an agent can separate the two 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 Guidelines4/5

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

It gives an explicit alternative and the condition that selects it: 'token_metadata when you need token facts read on chain.' What's missing is guidance on the reverse case — when to omit the optional chain filter, or when a broader multi-chain search is wasteful versus a single-chain lookup.

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