Skip to main content
Glama

Blazar Polygon plugin

Quote any token pair (Polygon, Base, Ethereum; aggregator)

blazar_any_quote
Read-onlyIdempotent

Quote ANY token pair on Polygon (default), Base or Ethereum (chain param; symbol from the chain's curated or KyberSwap verified list, or any 0x address) through KyberSwap and LI.FI (same-chain only, compared; best output wins), with Velora (ParaSwap) as automatic fallback. compared[] shows which aggregators answered. Covers Uniswap V3/V4, QuickSwap V3, Aerodrome and 100+ venues. Returns amountOut, USD in/out, usdLossBps, gas, venues and the router. Use for non-BZB pairs such as USDC->WETH; for BZB or BBY use blazar_quote (fee router, trading rewards). Read-only; quotes cached ~8 s.

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

Input Schema

NameRequiredDescriptionDefault
chainNoChain: "polygon" (default, chain 137), "base" (8453) or "ethereum" (1). BZB / BlazarSwap tools are Polygon only.
amountYesAmount of tokenIn in HUMAN units, not wei: "1.5" = 1.5 POL, "250" = 250 BZB. Set amountIsBaseUnits=true to pass wei/base units instead.
tokenInYesToken to sell: a symbol (USDC, WETH, AAVE, LINK...; resolved only via the chain's curated list or an exact unique KyberSwap-verified match) or any 0x token address on the chosen chain. Native coin: "POL" on Polygon, "ETH" on Base / Ethereum.
providerNoauto (default): KyberSwap and LI.FI compared, best output wins; Velora as fallback. Same-chain swaps only.
tokenOutYesToken to buy: a symbol (USDC, WETH, AAVE, LINK...; resolved only via the chain's curated list or an exact unique KyberSwap-verified match) or any 0x token address on the chosen chain. Native coin: "POL" on Polygon, "ETH" on Base / Ethereum.
amountIsBaseUnitsNoIf true, amount is in base units (wei for 18-decimal tokens; 6 decimals for USDC). Default false.

Output Schema

NameRequiredDescriptionDefault
chainNo
routeNo
cachedNo
gasUsdNo
routerNo
venuesNo
chainIdNo
spenderNo
summaryNo
tokenInNo
amountInNo
comparedNo
gasUnitsNo
providerNo
quotedAtNo
tokenOutNo
warningsNo
amountOutNo
routeGuideNo
usdLossBpsNo
amountInUsdNo
amountOutUsdNo
tokenInSourceNo
tokenOutSourceNo
rewardsEligibleNo
amountInFormattedNo
amountOutFormattedNo
quoteMaxAgeSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already establish read-only/idempotent/open-world, and the description adds information those cannot: aggregators are compared and best output wins, Velora is an automatic fallback, results are cached ~8 s, and compared[] reveals which aggregators responded. That caching note in particular prevents an agent from over-interpreting a slightly stale quote.

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?

It is front-loaded with the capability, chain scope and routing before the tail of return fields and the sibling hand-off. Dense parenthetical nesting makes it heavier than necessary, and listing output fields is partly redundant with the output schema, but no sentence is filler.

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 6-parameter quoting tool with annotations and an output schema, nothing an agent needs to call it correctly is missing: default chain, fallback behavior, same-chain restriction, symbol-vs-address resolution, and the sibling to use instead for BZB. Return values are covered by the output schema, so the brief mention here is sufficient rather than load-bearing.

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 all six parameters are already documented in the schema, including chain enum, human-units amount, symbol resolution and amountIsBaseUnits. The description largely restates that (chain default, symbol resolution, provider auto-compare), adding only the marginal clarification that provider comparison is same-chain only. Baseline 3 is appropriate.

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 ("Quote ANY token pair") plus the exact chains, the aggregators used (KyberSwap, LI.FI, Velora fallback), and the return shape. It explicitly carves out its scope against the sibling blazar_quote by naming BZB/BBY as the other tool's domain.

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?

Gives a concrete use case ("non-BZB pairs such as USDC->WETH") and an explicit when-not with the alternative named ("for BZB or BBY use blazar_quote"). The same-chain-only restriction is also stated, removing the main ambiguity an agent would hit.

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