Skip to main content
Glama

Quote a Polygon swap (BZB, POL, USDC...)

blazar_quote
Read-onlyIdempotent

Price a Polygon swap (POL, WPOL, BZB, BBY, USDC, USDT, WETH, WBTC, M421) before trading. Use this, not a generic DEX quote, when the user wants BZB or BZB trading rewards: it runs the deployed BlazarFeeRouter math over BlazarSwap, QuickSwap V2 and SushiSwap V2 and returns amountOut, priceImpactBps, venue, warnings[] (shallow pool, high impact, 5 bps wrapper fee vs a direct pool swap), and sizing (largest size under 1% and 5% impact). Read-only. Example: 1 POL -> 12.77 BZB via QuickSwap V2, 36 bps impact.

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_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
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: symbol (POL, WPOL, BZB, USDC, USDT, WETH, WBTC) or its listed 0x address (see blazar_tokens). "POL" is the native gas token; WPOL is the ERC-20.
tokenOutYesToken to buy: symbol (POL, WPOL, BZB, USDC, USDT, WETH, WBTC) or its listed 0x address. Choose "POL" to receive native POL (auto-unwrapped).
amountIsBaseUnitsNoIf true, amount is in base units (wei for 18-decimal tokens; 6 decimals for USDC). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only say readOnly/idempotent/openWorld; the description goes well beyond by disclosing the pricing engine (deployed BlazarFeeRouter math across three venues), the returned fields (amountOut, priceImpactBps, venue, warnings[], sizing thresholds), and a concrete fee caveat (5 bps wrapper fee vs a direct pool swap). That fee/warning disclosure is exactly the kind of behavior an agent needs before recommending a trade.

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?

Front-loads what it does and the key differentiator, then packs return fields, warnings and an example into one dense paragraph with no filler. It is on the long side and the return-field list could be set off more structurally, but nothing is redundant given there is no output schema.

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?

With no output schema, the description correctly compensates by naming every returned field and the warning categories, so an agent can interpret results. Minor gaps: no statement on quote freshness/expiry or on which sibling to call next (e.g. a build-swap tool) once a quote is accepted.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns one extra point for the worked example ("1 POL -> 12.77 BZB") that concretely demonstrates how amount/tokenIn/tokenOut compose. It still adds no detail on amountIsBaseUnits or address-vs-symbol handling beyond what the schema already states.

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 ("Price a Polygon swap"), enumerates the supported token set, and explicitly distinguishes itself from a generic DEX quote by naming the BZB/BZB-rewards use case and the BlazarFeeRouter/BlazarSwap/QuickSwap/SushiSwap venues it covers.

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 an explicit when-to-use condition ("when the user wants BZB or BZB trading rewards") plus a when-not ("not a generic DEX quote"), so an agent can route between this and a general quoter without inspecting schemas. It also flags that this is a pre-trade read-only step by saying "before trading".

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