Skip to main content
Glama

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?'

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive) and openness, so the description's added value is the result shape: each row carries rewardsEligible, buildableHere and behindBestBps, and the ParaSwap leg is a public API needing no key. It stops short of noting latency, rate limits, or what happens when a venue is unreachable.

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 the comparison scope, then the output fields, then the trigger phrase; every clause carries information. The opening sentence is long and enumerative, but the density is justified by the number of venues and route types being compared.

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 usefully names the per-row fields an agent will receive and clarifies that one leg is an external reference price rather than an executable route. Remaining gaps (error behavior, how many rows to expect, ordering of results) are minor for a read-only comparison tool.

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% and the per-parameter text (human units vs base units, POL vs WPOL, address-or-symbol) already carries the semantics. The description adds no parameter-level meaning of its own, 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?

States a specific verb (compare) and scope (one swap across venues) and enumerates exactly what is compared: the BlazarFeeRouter best route, per-venue best routes (BlazarSwap, QuickSwap V2, SushiSwap V2) both via router and direct pool, plus a ParaSwap reference. An agent can distinguish this from the build/quote siblings without opening a schema.

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 an explicit trigger ("Use when the user asks 'is this the best price?'") and frames it as a pre-trade, read-only step, which implicitly routes the agent to the build_swap siblings afterward. It does not explicitly name an alternative such as blazar_quote or blazar_prices and say when those win instead.

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