Skip to main content
Glama

Polymarket, Kalshi, Hyperliquid Funding Arbitrage & DEX Swap MCP

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

quote_low_fee_dex_swap
Read-onlyIdempotent

Quotes optimal non-custodial DEX swap output across Base (8453), Arbitrum (42161), Polygon (137), Optimism (10), and Ethereum (1) at 0.25% partner fee, saving 71% 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. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description usefully adds the 0.25% partner fee, non-custodial nature and a cost comparison, but omits behavior an agent needs, notably quote validity/staleness, slippage assumptions and whether the output amount is guaranteed.

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 front-loaded sentence with the resource and chain scope stated first. The trailing "saving 71% vs 0.875% wallet built-in swaps" is promotional rather than actionable and consumes space that could have carried quote-freshness or workflow guidance.

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?

With four fully documented parameters and annotations covering safety, the definition is close to sufficient, but with no output schema the agent gets no hint of what a quote returns (expected output amount, route, fee breakdown). Given it is a quoting tool feeding a calldata builder, that missing return context is a real gap.

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% and every parameter is documented in-schema, so baseline applies. The description largely restates the chain coverage already enumerated in the chainId field and adds no extra meaning such as default routing, symbol case-sensitivity or amount precision.

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 specific verb and resource ("Quotes optimal non-custodial DEX swap output") plus the exact chains and fee tier, so an agent knows precisely what it returns. It does not differentiate itself from the sibling build_smart_dex_swap_calldata, so a quote-versus-execute distinction must be inferred from the names alone.

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: "quote" suggests previewing a swap before building calldata, but the description never states when to use this versus the execution sibling or any prerequisite. There are no exclusions or conditions, leaving the agent to infer the quoting stage of the workflow.

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.