Skip to main content
Glama

Ellimist

Build swap transaction (non-custodial)

exchange_build_swap
Read-only

Unsigned approval + swap transactions for the best route. Your agent signs and broadcasts from its own wallet; Ellimist never takes custody. Conversions are executed by third-party smart contracts (routed by LI.FI) that may fail or be exploited; funds may be lost and transactions are irreversible. Price: $0.005 USDC per call via x402 (no account). Not charged if it fails.

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": {
      "from_chain": "<from_chain>",
      "to_chain": "<to_chain>",
      "from_token": "<from_token>",
      "to_token": "<to_token>",
      "from_amount": "<from_amount>",
      "from_address": "<from_address>"
    },
    "name": "exchange_build_swap"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderNoCHEAPEST
slippageNo
to_chainYes
to_tokenYessymbol (ETH) or token address
from_chainYes
from_tokenYessymbol (USDC) or token address
to_addressNo
from_amountYesamount in the token's smallest unit
from_addressYes
allow_high_impactNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Goes well past the annotations: it discloses non-custody, third-party contract execution risk (may fail or be exploited), irreversibility and possible loss of funds, plus a concrete pricing model ($0.005 USDC per call via x402, no account, not charged on failure). This also explains why readOnlyHint=true despite the word 'swap' — the server only builds unsigned payloads. That is exactly the extra context annotations cannot carry.

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 dense sentences, front-loaded with what the tool produces, then custody model, then risk, then price. No filler and no repetition of the tool name or title.

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, and the description covers the important part of the return — an unsigned approval plus swap transaction the agent must sign. Risk, custody, and cost are all disclosed. The remaining gap is parameter-level meaning for the six required and four optional inputs, which is a schema-side deficiency more than a description one.

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

Parameters2/5

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

Schema description coverage is only 30% across 10 parameters, so the description needs to compensate and does not. It says nothing about order (CHEAPEST/FASTEST), slippage bounds, to_address defaulting, or — most importantly — allow_high_impact, whose safety implication (bypassing a price-impact guard) is left entirely unexplained.

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?

States a concrete verb and resource: it builds unsigned approval + swap transactions for the best route, with the routing provider (LI.FI) named. An agent can tell this apart from a quote-style sibling because the output is described as transactions to sign, not a price. It stops short of explicitly naming the sibling it complements, so not a 5.

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 description gives real context for use — the agent signs and broadcasts from its own wallet, and Ellimist never takes custody — which implies the intended caller flow. However it never says when to pick this over exchange_quote or exchange_status, nor what prerequisites (e.g., allowance, balance, supported chains) must hold first. Usage is implied rather than directed.

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