Skip to main content
Glama

Blazar Polygon plugin

TWAP plan (dry run)

blazar_plan_twap
Read-onlyIdempotent

Dry-run TWAP planner: splits a swap into N slices every intervalSeconds and compares with one swap now (impact per slice, estimated gain in bps, schedule with min-out per slice). Never sends anything; build each slice with blazar_build_swap when it is due. 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>",
      "slices": "<slices>",
      "intervalSeconds": "<intervalSeconds>"
    },
    "name": "blazar_plan_twap"
  }
}

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.
slicesYesNumber of equal slices, 2-48.
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).
slippageBpsNoPer-slice slippage for min-out. Default 50.
intervalSecondsYesSeconds between slices, 30-86400.
amountIsBaseUnitsNoIf true, amount is in base units (wei for 18-decimal tokens; 6 decimals for USDC). Default false.

Output Schema

NameRequiredDescriptionDefault
dryRunNo
slicedNo
oneShotNo
summaryNo
scheduleNo
assumptionsNo
perSliceToolNo
recommendationNo
durationSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/non-destructive, and the description reinforces this with 'Never sends anything', which matters for a tool whose name suggests a trade. It also discloses what the result contains (per-slice impact, estimated gain in bps, schedule with min-out per slice) and the Polygon-only limitation, though the output schema carries most of the return-value detail.

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 dense sentences with the purpose and output shape first, the safety/next-step clause second, and the chain limitation last; no filler or restatement of the title.

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?

For a 7-parameter planning tool with a full output schema and safety annotations, the description covers the remaining gaps an agent needs: it is a dry run, what it returns at a high level, how to proceed to execution, and which chain is supported.

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% and each parameter is individually documented (human vs base units, slice range, interval range, slippage default). The description echoes slices/intervalSeconds but adds no format or constraint detail beyond what the schema already states, so the schema is doing the work.

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 ('Dry-run TWAP planner: splits a swap into N slices every intervalSeconds') and explicitly says what it is compared against ('one swap now'), so an agent can distinguish it from quote/build siblings without opening a schema. The Polygon-only scope is stated up front.

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

Usage Guidelines5/5

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

Explicitly frames this as a non-executing planning step ('Never sends anything') and names the correct follow-up action with its trigger condition ('build each slice with blazar_build_swap when it is due'). The chain restriction (137 only) further narrows when it is applicable.

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