Skip to main content
Glama

Ellimist

Supported chains and tokens

exchange_supported
Read-only

Use this (free) to see which chains Ellimist can convert between and, for one chain, which tokens with their USD prices. Price: $0 USDC per call via x402 (no account). Not charged if it fails.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "exchange_supported"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNochain name or id; include its tokens with prices

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered, and the description still adds genuinely new behavior: $0 USDC per call via x402, no account required, and no charge on failure. Those are billing and authentication facts an agent cannot get from the annotations or schema. It does not describe response shape or any rate limits, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, both front-loaded: capability first, commercial terms second. Every clause carries information the agent needs — what it returns, what it costs, and that failure is free. No filler or restatement of the tool name.

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?

There is no output schema, so the description has to sketch the return values, and it does: a chain list, plus tokens and USD prices when a chain is supplied. Combined with annotations covering read-only/open-world behavior, an agent has enough to call this correctly. Only the response format and ordering are unspecified, which is minor for a catalog tool.

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% and the single optional chain parameter is documented, so the baseline would be 3. The description earns an extra point by explaining the conditional behavior of that parameter: with no chain you get the list of chains, and with one chain you additionally get its tokens with USD prices. That is real meaning beyond the schema's 'chain name or id' text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: see which chains the service can convert between, and for a single chain, which tokens with USD prices. That is concrete enough to distinguish it from exchange_quote and exchange_build_swap, which act on a known pair rather than enumerate options. It does not name a sibling, so differentiation is inferred from the resource rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The opening 'Use this (free) to see...' frames the tool as a discovery call, and the price note makes it clear this is the cheap way to explore before committing to a quote or swap. However, there is no explicit when-not guidance or named alternative, so the sequencing (call this first, then exchange_quote) is left to the agent to infer.

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