Agent Kiosk

defi_swap_quote

Read-onlyIdempotent

Build ready-to-sign EVM transaction calldata for DeFi swaps and cross-chain bridges. It queries LI.FI and ParaSwap for DEX and bridge routes across Base, Ethereum, Arbitrum, Polygon, and Optimism.

Instructions

Executable DeFi Swap & Cross-Chain Bridge Action Calldata Builder ($0.05 USDC). Queries LI.FI and ParaSwap aggregators to compute the best DEX/Bridge route and returns ready-to-sign EVM transaction calldata (to, data, value, gasLimit) on Base, Ethereum, Arbitrum, Polygon, and Optimism.

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_token": "<from_token>",
      "to_token": "<to_token>"
    },
    "name": "defi_swap_quote"
  }
}

Input Schema

Name	Required	Description
`amount`	No	Amount of from_token to swap (human-readable e.g. '10' or atomic units)
`wallet`	No	Optional 0x sender wallet address for transaction simulation
`to_chain`	No	Destination blockchain network (default: same as from_chain)
`to_token`	Yes	Destination token symbol (e.g., 'ETH', 'USDC', 'AERO', 'cbBTC') or 0x address
`from_chain`	No	Source blockchain network (default: 'base')
`from_token`	Yes	Source token symbol (e.g., 'USDC', 'ETH', 'AERO') or 0x contract address

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.5.0Oct 18, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnlyHint, idempotentHint, openWorldHint, destructiveHint=false), so the bar is lower. The description adds real value beyond them: the aggregators queried, the $0.05 USDC cost, the exact calldata fields returned, and the supported chains. It does not mention slippage, latency, or failure modes, keeping 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?

Two dense sentences, front-loaded with the tool's identity and output, with no filler. The parenthetical pricing and chain list are compact. Slightly packed but every clause carries 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?

No output schema exists, and the description compensates by naming the return fields (to, data, value, gasLimit), which is the key information an agent needs. Cost and supported chains are also covered. Missing only secondary details like slippage handling or the difference between quoting and executing.

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 100%, so the schema already documents all six parameters including defaults for from_chain/to_chain and enum values. The description adds only the chain list, which duplicates the enum. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Executable DeFi Swap & Cross-Chain Bridge Action Calldata Builder') and names the mechanism (LI.FI and ParaSwap aggregators) plus the exact output payload (to, data, value, gasLimit). This clearly distinguishes it from read-only data siblings like defi_yields or token_alpha.

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 'Action Calldata Builder' framing implies this is the execution-prep step rather than a data lookup, and the named chains give context. However, it never states when to use this versus other DeFi siblings, nor any prerequisites or exclusions. Usage is implied, not specified.

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