Skip to main content
Glama

Blazar Polygon plugin

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. Polygon only (chain 137).

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.

Output Schema

NameRequiredDescriptionDefault
noteNo
routeNo
venueNo
sizingNo
chainIdNo
summaryNo
tokenInNo
amountInNo
tokenOutNo
warningsNo
amountOutNo
wrapperFeeNo
alternativesNo
wrapperFeeBpsNo
priceImpactBpsNo
rewardsEligibleNo
amountInFormattedNo
amountOutFormattedNo
directPoolAmountOutNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, the description discloses routing across BlazarSwap, QuickSwap V2, and SushiSwap V2, explains that it returns warnings for shallow pools, high impact, and the 5 bps wrapper fee, and notes sizing outputs. It also states Polygon-only scope and gives a concrete quote example, adding substantial behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with purpose and usage, then adds routing, outputs, warnings, and scope in dense but useful sentences. The example and parenthetical token lists are informative rather than redundant, and no sentence feels like 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?

Given that an output schema exists and all four parameters have full schema descriptions, the description supplies the remaining context an agent needs: Polygon-only scope, the specific venue routing, warning conditions, sizing outputs, and the BZB-rewards use case. Nothing essential for correct selection or invocation is missing.

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 input schema already documents tokenIn, tokenOut, amount, and amountIsBaseUnits thoroughly. The description adds a useful example but does not add parameter meaning beyond what the schema provides; 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?

The description uses a specific verb and resource: 'Price a Polygon swap ... before trading.' It clearly scopes the tool to Polygon (chain 137) and distinguishes it from a generic DEX quote by naming BlazarFeeRouter math over BlazarSwap, QuickSwap V2, and SushiSwap V2.

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

Usage Guidelines4/5

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

It gives a clear use condition — before trading and when the user wants BZB or BZB trading rewards — and explicitly says to use this rather than a generic DEX quote. It does not contrast with sibling quote tools such as blazar_any_quote for non-BZB cases, leaving a small gap in alternative selection.

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