SiteCheck Crypto & Finance

Best swap quote for a token pair on an EVM chain, compared

crypto_1inch_pathfinder_quotes

Read-only

Best swap quote for a token pair on an EVM chain, compared across two public DEX aggregators (KyberSwap and Velora/ParaSwap): amount out, USD values, estimated gas in USD, price impact against the input's USD value and the pools/DEXes used, plus which aggregator gives more. Chains: Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain, Avalanche. Indicative quotes, not executable orders. Related tools on this server, for a different need: crypto_sushiswap_route_quotes when you need SushiSwap route quote for an exact-input swap on one EVM. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "tokenIn": "<tokenIn>",
      "tokenOut": "<tokenOut>",
      "amount": "<amount>"
    },
    "name": "crypto_1inch_pathfinder_quotes"
  }
}

Input Schema

Name	Required	Description
`chain`	No	ethereum, base, arbitrum, optimism, polygon, bsc or avalanche (default ethereum)
`amount`	Yes	Amount of tokenIn in whole units, e.g. 1.5
`tokenIn`	Yes	Token to sell: contract address, or native for the chain's coin
`tokenOut`	Yes	Token to buy: contract address, or native

Output Schema

Name	Required	Description	Default
`best`	No
`chain`	No
`quotes`	No
`source`	No
`tokenIn`	No
`amountIn`	No
`tokenOut`	No
`checkedAt`	No
`decimalsIn`	No
`decimalsOut`	No
`spreadPercent`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond readOnlyHint/openWorldHint, it discloses that quotes are indicative rather than executable, that results aggregate exactly two named aggregators, and the commercial terms: $0.002 USDC per successful call via x402 on Base/Solana/Arc with failed calls uncharged. Cost and success-billing behavior are things annotations cannot convey.

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?

Purpose is front-loaded in the first clause, and the pricing/alternative sentences are short and useful. Minor waste: the chain list and the payout currencies duplicate what the schema and annotations already establish.

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

Completeness5/5

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

For a read-only priced quote endpoint, the definition covers the compared venues, supported chains, the meaning of the output fields, cost, failure billing, and the nearest alternative. An output schema exists, so no further return-value detail is required.

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 every parameter is already documented in the schema with examples (whole units, 'native' sentinel, chain list). The description's re-listing of supported chains and its note about comparing against input USD value add little beyond that, so the baseline 3 applies.

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?

The description names a specific verb and resource ("best swap quote for a token pair"), states the comparison source (KyberSwap vs Velora/ParaSwap), enumerates the returned fields, and explicitly distinguishes itself from the SushiSwap route-quote sibling. An agent can select it without opening the schema.

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

Usage Guidelines5/5

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

It gives an explicit routing rule ("crypto_sushiswap_route_quotes when you need SushiSwap route quote for an exact-input swap on one EVM") plus a clear exclusion ("Indicative quotes, not executable orders"). Both when-to-use and when-not-to-use are covered.

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

All SiteCheck Crypto & Finance tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?