xswap.to

Search currencies

search_currencies

Read-only

Find coins and tokens by symbol, name or network and get their currency ids. Each id is one coin on one network: usdttrc20 is USDT on TRON, usdterc20 is USDT on Ethereum. Use the ids in get_quote and create_swap.

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_currencies"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Most results to return.
`query`	Yes	Symbol, name or network, for example "usdt", "usdt tron" or "solana".

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false and the description does not contradict them. It adds genuine domain knowledge beyond the annotations — that currency ids are network-scoped, illustrated with the USDT TRON vs Ethereum pair — which prevents the common failure of assuming one id per ticker. It stops short of describing result shape or behavior on no-match queries.

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 action and output, then the id-semantics disambiguation, then the downstream routing. Every sentence earns its place and nothing repeats the schema verbatim.

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 carries the burden of explaining return values, and it does so for the most important field (the currency id) with a concrete disambiguation. Minor gap: it doesn't describe the other result fields an agent might need when picking among multiple matches, or behavior when the query is ambiguous.

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 both the query and limit parameters are already documented with examples and bounds. The description's 'symbol, name or network' restates the schema's query description and adds no syntax or matching-rule detail (e.g. case sensitivity, substring vs exact), so baseline 3 applies.

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 ('Find coins and tokens') plus the keyed output ('get their currency ids'), and immediately disambiguates what an id actually represents by contrasting usdttrc20 with usdterc20. An agent knows exactly what this tool returns without opening the 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?

Explicitly routes the agent forward: the returned ids are to be used in get_quote and create_swap, which establishes this as the prerequisite lookup step. No sibling is a competing search tool, so no exclusion is needed, though the description never states what to do with an ambiguous or empty result.

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

All xswap.to tools Inspect

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

Need Help?