Skip to main content
Glama

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.

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).

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?

Annotations already say readOnlyHint=true and destructiveHint=false, and the description is consistent with that by stressing the tx is UNSIGNED, so nothing is mutated server-side. It adds real behavioral value the annotations do not: the zero-amount NOTHING_TO_CLAIM outcome and the fact that a simulation is bundled in. It does not state the allowance/nonce preconditions beyond what lives in the schema.

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?

A single dense sentence, front-loaded with the core action and followed by return-shape details and the edge case; no filler. The NOTHING_TO_CLAIM clause is slightly compressed but still unambiguous.

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 only two fully documented parameters and no output schema, the description usefully carries the return contract (unsigned tx, summary, simulation, sentinel), which is exactly what the missing output schema would have provided. Remaining gaps, such as the next step of signing/sending and pagination-free error handling, are minor for a build-only 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 schema already explains 'from' (allowance checks, simulation, nonce) and 'dayId' (with the floor(unixSeconds/86400) formula and a source pointer). The description only restates that a day and amount are involved, adding no syntax or format detail, so 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') and enumerates the return payload: claim tx, summary, simulation, and a NOTHING_TO_CLAIM sentinel. It implicitly separates itself from preview-style siblings by saying it returns an unsigned tx, though it never names an alternative.

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?

Usage is implied by the description ('one call to claim') and the dayId parameter points to blazar_daily_rewards for sourcing the day, but there is no explicit when-to-use vs when-not, and no routing against blazar_trading_rewards_preview or blazar_daily_claimable. The agent must infer sequencing (build, then sign, then send).

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