Skip to main content
Glama

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.

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.

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, idempotentHint and destructiveHint=false, so the safety bar is low, yet the description still adds real substance: the price is 'executable' and inclusive of fees and price impact, and the call returns triggered, gapBps and pre-built swap args. 'Never sends anything' reinforces the dry-run nature. It does not specify edge behavior, such as what gapBps is measured against when not triggered.

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?

Two tight sentences with the core question front-loaded, followed by the return contract and the no-side-effect guarantee. No filler or restated boilerplate.

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?

There is no output schema, so the description must name the return fields, and it does: triggered, gapBps, and the exact blazar_build_swap args. Combined with the dry-run guarantee, an agent has enough to call and interpret it. Minor gaps remain, such as the units/meaning of gapBps and what happens to the suggested args when the limit is not met.

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 coverage is 100%, with amount units, token symbols and limitPrice direction all documented in the schema itself. The description restates limitPrice as 'tokenOut per 1 tokenIn' and clarifies that the price depends on size, but adds no format, range or unit detail beyond the structured fields. Baseline 3 is appropriate when the schema carries the parameter burden.

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 ('Off-chain limit-order check') plus the exact predicate being evaluated: whether the executable BlazarFeeRouter price for this size, after fees and impact, is at or above limitPrice. It also names the downstream artifact (the exact blazar_build_swap args), so an agent can distinguish it from a plain quote tool without opening the 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?

The framing 'check for a bot' plus 'returns the exact blazar_build_swap args to use' makes the intended workflow clear: gate first, then build the swap. It stops short of explicit when-not guidance, e.g. when to prefer blazar_quote or blazar_compare_venues for pricing rather than a threshold check, so it is strong context but not full routing.

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