Skip to main content
Glama

Blazar Polygon plugin

Limit-order check (dry run)

blazar_check_limit
Read-onlyIdempotent

Off-chain limit-order check for a bot: is the executable BlazarFeeRouter price for this size (after fees and impact) at or above limitPrice (tokenOut per 1 tokenIn)? Returns triggered, gapBps and the exact blazar_build_swap args to use. Never sends anything. 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>",
      "limitPrice": "<limitPrice>"
    },
    "name": "blazar_check_limit"
  }
}

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).
limitPriceYesMinimum tokenOut per 1 tokenIn, e.g. "12.5" BZB per POL.
amountIsBaseUnitsNoIf true, amount is in base units (wei for 18-decimal tokens; 6 decimals for USDC). Default false.

Output Schema

NameRequiredDescriptionDefault
nextNo
noteNo
gapBpsNo
statusNo
amountInNo
amountOutNo
priceUnitNo
triggeredNo
limitPriceNo
priceImpactBpsNo
executablePriceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real context beyond them: the check is off-chain, it accounts for fees and price impact rather than raw mid price, it sends nothing, and it is restricted to chain 137 — a constraint an agent could otherwise miss. It does not discuss behavior on unsupported tokens or how a negative gap is reported, keeping it out of the top score.

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?

Three tight sentences, front-loaded with what is computed and in what order, followed by the return payload and the two hard constraints (read-only, Polygon only). No filler or repetition of the title.

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 an output schema present, the returned fields (triggered, gapBps, build args) need not be detailed, and the definition still gives the decision rule and chain restriction that determine a correct call. Minor gaps remain: no guidance on whether price impact tolerance is configurable or what happens for tokens outside the listed set.

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 schema already explains amount units, symbol-vs-address inputs, amountIsBaseUnits and the limitPrice pattern. The description only restates the limitPrice orientation ('tokenOut per 1 tokenIn'), which the schema also states, and adds no new per-parameter nuance. 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: an off-chain limit-order check that compares the executable BlazarFeeRouter price (after fees and impact) against limitPrice for a given size. It also fixes the unit convention (tokenOut per 1 tokenIn) and the chain (Polygon 137), which separates it cleanly from blazar_quote, blazar_any_quote and blazar_build_swap.

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?

The dry-run framing plus 'Returns ... the exact blazar_build_swap args to use' and 'Never sends anything' makes the workflow role explicit: check here, then build with blazar_build_swap. It stops short of naming when a caller should prefer blazar_quote or blazar_any_quote instead, so coverage of alternatives is partial.

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