Skip to main content
Glama

Claimable trading reward

blazar_daily_claimable
Read-onlyIdempotent

How much BZB one address can claim for one posted trading-reward day. Read-only. Get dayId from blazar_daily_rewards.postedDays.

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>",
      "account": "<account>"
    },
    "name": "blazar_daily_claimable"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayIdYesUTC day number of the trades = floor(unixSeconds / 86400), e.g. "20773" = 2026-11-16. Get it from blazar_daily_rewards (todayDayId, postedDays[].dayId).
accountYesAddress to check.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so repeating 'Read-only' adds nothing. The description does add the meaningful constraint that only posted days are queryable, but it omits what happens for a non-posted day, whether a zero result is possible, and what unit/decimals the returned BZB amount uses.

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?

Three short sentences, front-loaded with what is returned and immediately followed by the dayId sourcing instruction. The only waste is the redundant 'Read-only' clause that duplicates an annotation, but it is a single word and does not bloat the definition.

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 two-parameter read with full schema coverage and no output schema, the definition covers purpose, prerequisite, and the nature of the returned value ('how much BZB'). It is nearly complete; the residual gap is the return value's units/precision and behavior on unposted days, which matter for interpreting the number.

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 both parameters are fully documented, including the day-number formula and address pattern, so the baseline is 3. The description reinforces the dayId provenance ('from blazar_daily_rewards.postedDays') but adds no semantics the schema does not already carry.

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?

The description gives a specific quantity, a specific unit (BZB), and precise scope (one address, one posted trading-reward day), which separates it from blazar_daily_rewards (day enumeration) and blazar_build_claim (transaction building). It stops short of naming those siblings explicitly, so the distinction relies on inference from the phrase 'one posted trading-reward day'.

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?

It supplies a concrete prerequisite and routing rule: obtain dayId from blazar_daily_rewards.postedDays, which tells the agent this is a second-step query rather than a starting point. There is no explicit when-not guidance (e.g. that today's unposted day cannot be queried), but the 'posted' qualifier implies it.

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