Skip to main content
Glama

Blazar Polygon plugin

Build trading-reward claim

blazar_build_claim
Read-only

One call to claim a posted BZB trading reward: the claim tx with a summary (amount and day), a simulation, and NOTHING_TO_CLAIM if the amount is 0. Returns an UNSIGNED tx. 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": {
      "dayId": "<dayId>",
      "from": "<from>"
    },
    "name": "blazar_build_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromYesAddress that will sign and send the txs. Required: used for allowance checks, simulation and nonce.
dayIdYesUTC day number of the trades = floor(unixSeconds / 86400), e.g. "20773" = 2026-11-16. Get it from blazar_daily_rewards (todayDayId, postedDays[].dayId).

Output Schema

NameRequiredDescriptionDefault
txsYesSign and send in order.
fromNo
nextNo
batchNoEIP-5792 wallet_sendCalls request with the same calls (smart wallets).
quoteNo
actionYes
guardsNo
safetyNo
chainIdNo137 Polygon, 8453 Base, 1 Ethereum. BlazarForce builds are always 137.
detailsNo
signingNo
summaryYes
warningsYes
routeGuideNo
simulationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Goes beyond the annotations in useful ways: it returns an unsigned transaction (so the agent knows signing/sending is its own responsibility), bundles a simulation and a summary, short-circuits with NOTHING_TO_CLAIM on zero amount, and is restricted to chain 137. It does not contradict readOnlyHint — building a tx is a read-only construction step. Missing: what the simulation covers or failure modes beyond the zero-amount case.

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?

Tight and front-loaded: the core action leads, then output form, then the zero-amount edge case, then the chain restriction. Dense colon-listing is slightly telegraphic but every clause carries information; nothing is wasted.

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?

For a 2-param builder with full schema coverage and an output schema, the description covers the essentials an agent needs: unsigned output, simulation, zero-amount branch, and chain restriction. It omits prerequisites such as allowance requirements (the 'from' param hints at allowance checks) and how to obtain a posted reward, which keeps it short of a 5.

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 both parameters (from, dayId) are already fully documented, including the floor(unixSeconds/86400) derivation and the pointer to blazar_daily_rewards. The description adds only that a day/amount summary is returned, which is not new parameter meaning — baseline 3 applies.

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?

States a specific verb and resource: 'claim a posted BZB trading reward' via 'One call', and makes explicit that the output is an UNSIGNED tx. It is distinguishable from build_swap or build_stake by naming the BZB trading-reward resource, though it does not call out a specific sibling for contrast.

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

Usage Guidelines3/5

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

It implies the precondition ('posted' reward) and encodes one branch behavior (NOTHING_TO_CLAIM when amount is 0), plus a hard chain constraint (Polygon 137). But there is no explicit when-to-use vs. alternatives guidance, e.g., no pointer to blazar_daily_claimable or blazar_trading_rewards_preview for checking claimability first — that routing only appears indirectly in the dayId schema description.

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