Skip to main content
Glama
Sign In

OpenFinance — Easy Trading: Crypto, Stocks, Perps & Prediction Markets

by tech.openfinance
OverviewDiscussionsAdmin

onchain_search_tokens

Multi-chain token search across 200+ chains. Pass either a free-text phrase (token name / symbol — "PEPE", "wrapped bitcoin", "shiba inu") OR a raw token address; both work through the same query field. Optionally scope to specific chains via networkIds (e.g. [1, 137, 8453] for Ethereum + Polygon + Base). Returns { count, results } where each result has the token (id, address, name, symbol, decimals, networkId, logo, description, blueCheckmark) plus live stats (priceUSD, volume24, change24, liquidity, marketCap). Use this BEFORE any other onchain tool when the user gives a token by name and you need the address+chain — e.g. "what's SHIB doing", "find PEPE", "is wrapped BTC at the right price". Avoid when the user already gave you {address, chainId} — go straight to onchain_get_token_metadata / onchain_get_token_usd_price.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 25, max 100).
queryYesPhrase (name/symbol) or raw token address. The wrapper passes it as Codex's `phrase` field which handles both forms.
offsetNoPagination offset.
networkIdsNoScope to specific chain IDs (e.g. [1, 137, 8453]). Omit for global search across every chain Codex covers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden and does much of it: it discloses the return envelope ({ count, results }), the fields per result including live stats, the dual query semantics, and the global-vs-scoped search behavior. It omits any auth/rate-limit or result-ranking caveats, which keeps it short of a 5.

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?

Front-loaded with purpose and scope, then parameter notes, then usage routing, then exclusions. Dense and largely waste-free, though the parenthetical example lists (quoted token names, result field enumeration) push toward the verbose side.

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?

With no output schema present, the description compensates by describing the { count, results } envelope and per-result fields, plus live stats. Combined with full schema coverage and complete usage routing, an agent has everything needed to select and invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds value beyond the schema by explaining that both a phrase and a raw address are accepted through the same `query` field and by giving a concrete `networkIds` example ([1, 137, 8453]) tied to named chains.

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 (search) and resource (tokens) with explicit scope: multi-chain, 200+ chains. Clearly distinguishable from siblings like onchain_get_token_metadata and onchain_get_token_usd_price, which it names directly.

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?

Gives explicit when-to-use (user supplies a token by name and you need address+chain, with concrete examples like 'find PEPE') and explicit when-not-to-use (user already has {address, chainId} → go to onchain_get_token_metadata / onchain_get_token_usd_price). Both routing conditions and alternatives are named.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All OpenFinance — Easy Trading: Crypto, Stocks, Perps & Prediction Markets 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