Skip to main content
Glama

Blazar Polygon plugin

Compare a swap across venues

blazar_compare_venues
Read-onlyIdempotent

Compare one swap across venues before trading: the best BlazarFeeRouter route, the best route on each single venue (BlazarSwap, QuickSwap V2, SushiSwap V2) through the fee router and as a direct pool swap, and a ParaSwap reference price (public API, no key). Each row says rewardsEligible and buildableHere, plus behindBestBps. Read-only. Use when the user asks 'is this the best price?' 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_compare_venues"
  }
}

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.
includeAggregatorNoInclude the ParaSwap reference price (public API). Default true.

Output Schema

NameRequiredDescriptionDefault
asOfNo
noteNo
venuesNo
summaryNo
tokenInNo
verdictNo
amountInNo
tokenOutNo
aggregatorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 description only needs to add context. It does add value: the ParaSwap leg hits a public API with no key, and the tool is Polygon-only (chain 137) — a real hard constraint. However, it duplicates 'Read-only' already in annotations and does not discuss latency, rate limits, or how a missing ParaSwap response is handled.

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

Conciseness3/5

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

Front-loaded with the purpose and free of filler, but the opening sentence is a long stacked list of route types that is dense to parse. The chain restriction is buried at the very end after the usage cue, where a reader may skim past it.

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 a full output schema and rich annotations, the description covers what the structured fields cannot: the venue set, the external ParaSwap dependency, the chain restriction, and the meaning of the per-row flags. Only minor operational details (latency, behavior when the public API is unavailable) are absent.

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%, including human-vs-base-unit semantics, symbol/address acceptance, and the includeAggregator flag, so the schema carries the parameter burden and the baseline of 3 applies. The description adds nothing parameter-specific beyond implying a single tokenIn/tokenOut/amount pair.

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?

Uses a specific verb ('Compare') plus the exact scope: one swap across the BlazarFeeRouter route, per-venue routes (BlazarSwap, QuickSwap V2, SushiSwap V2) via router and direct pool, and a ParaSwap reference. That enumeration makes it distinguishable from quote-only siblings in substance. It never names a sibling like blazar_quote or blazar_any_quote, so full marks for sibling differentiation are not earned.

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?

Gives a concrete usage trigger ('Use when the user asks "is this the best price?"') and a timing cue ('before trading'), which is more than most definitions offer. It stops short of explicit when-not guidance or naming the cheaper alternative (blazar_quote) for a single-venue price check.

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