Skip to main content
Glama

AINDEX

Find a token by ticker, name or address

search_tokens
Read-only

Turn a ticker, name or address prefix into a token address. Verified tokens come first, and a token that only shares a verified token's ticker is flagged. Many tokens share tickers: hundreds of launches call themselves NVDA. Unverified results show liquidity, 24h volume and holders; get_token_market has more.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesA ticker, name, or address prefix.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral value beyond that: verified tokens are ranked first, ticker-squatters are flagged, and unverified results carry liquidity/volume/holder fields. It does not state result ordering beyond verification, pagination, or whether a miss returns empty vs. error.

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?

Three short sentences, front-loaded with the core transformation, then ranking behavior, then the sibling pointer. No filler and every sentence contributes new information.

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 no output schema, the description helpfully previews what unverified results contain. It leaves the limit parameter and the shape of verified-token results unexplained, a minor gap for a 2-parameter read-only lookup.

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 50%: the query parameter is documented in the schema and merely restated here, while limit (default 8, max 25) is never mentioned in the description. Baseline 3 applies since the description neither documents the undocumented parameter nor adds syntax 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?

Opens with a precise verb+resource transformation ("Turn a ticker, name or address prefix into a token address") and explicitly contrasts scope with get_token_market, so the agent can distinguish this lookup/resolve tool from a market-data tool 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?

Explains the ambiguity motivating the tool ("hundreds of launches call themselves NVDA") and points to get_token_market for deeper data, giving clear context for when this is the right entry point. There is no explicit 'do not use for X' exclusion, which keeps it just below a 5.

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