Skip to main content
Glama

DeFi Funding Arbitrage, Pendle & Prediction Odds MCP

Quote 0.15% Low-Fee Non-Custodial EVM DEX Swap

quote_low_fee_dex_swap
Read-onlyIdempotent

Quotes optimal KyberSwap MetaAggregationRouterV2 non-custodial DEX swap output across Base (8453), Arbitrum (42161), Polygon (137), Optimism (10), and Ethereum (1) at 0.15% partner fee, saving 83% vs 0.875% wallet built-in swaps.

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

Input Schema

NameRequiredDescriptionDefault
amountNoHuman-readable input amount (default 1000)
chainIdNoEVM chain ID ('8453' Base, '42161' Arbitrum, '137' Polygon, '10' Optimism, '1' Ethereum)
srcSymbolNoInput token symbol (e.g. 'USDC', 'ETH', 'USDT', 'WETH')
destSymbolNoOutput token symbol (e.g. 'ETH', 'USDC', 'WBTC', 'cbBTC')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real context beyond them: a 0.15% partner fee, non-custodial execution via a named router, and the exact chain set. It stops short of behavior an agent would want, such as quote expiry/route freshness or whether the returned quote is directly executable.

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?

A single dense sentence with the core purpose front-loaded. The closing comparison ('saving 83% vs 0.875% wallet built-in swaps') is promotional rather than operational and doesn't help an agent invoke the tool, but it is brief and does not obscure the actionable content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description carries the burden of explaining what a quote returns, yet it says nothing about the response shape (expected output amount, route path, gas estimate, price impact) or quote validity. For a multi-chain aggregator quote this leaves a meaningful gap, though the input semantics and safety profile are adequately covered.

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 the schema already documents all four parameters, including chain IDs and example token symbols. The description only restates the same chain-ID mapping and adds no format, default, or constraint detail beyond it; baseline 3 applies. It also does not clarify that all four parameters are optional/zero-required, which could lead an agent to omit essentials.

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?

Names a specific verb + resource ('Quotes... DEX swap output'), the exact aggregator (KyberSwap MetaAggregationRouterV2), the supported chains with IDs, and the fee tier. An agent can tell immediately that this is a read-only price quote for an EVM token swap, which is distinct from every sibling (bridge, kimchi premium, Pendle, funding scans).

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?

Usage is only implied: the word 'Quotes' plus the amount/chainId/srcSymbol/destSymbol parameters make it clear this prices a swap rather than executing one. There is no explicit when-to-use/when-not, no mention of prerequisites (token approvals, liquidity/slippage limits), and no comparison to a sibling tool for actually executing the swap.

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.