Skip to main content
Glama

Blazar Polygon plugin

Trading rewards: status and posted days

blazar_daily_rewards
Read-onlyIdempotent

BZB daily trading-rewards status for swaps through BlazarFeeRouter: today's dayId, recently posted days with totals and claim deadlines, daily cap, contract balance, and scoring rules. Use it to find a dayId before blazar_daily_claimable or blazar_build_claim. Polygon only (chain 137).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "blazar_daily_rewards"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
rulesNo
pausedNo
statusNo
contractNo
dailyCapNo
postedDaysNo
todayDayIdNo
dayIdFormatNo
totalPostedNo
campaignStartDayNo
currentBucketDayNo
reservedForClaimsNo
claimWindowSecondsNo
contractBzbBalanceNo

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, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds value beyond them by disclosing the data surface (cap, contract balance, deadlines), the chain restriction, and the sequencing role relative to claim tools. It does not mention auth/wallet requirements or freshness/latency of the posted-days data.

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 sentences, both front-loaded: the first states what is returned, the second states when to call it and the chain constraint. The enumerated field list is dense but each item is meaningful, with no filler or repetition 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 zero-parameter read tool with a rich annotation set and an output schema, the description supplies everything an agent needs: purpose, returned data, chain scope, and the workflow position relative to claim-building tools. Return-value formatting needn't be repeated since an output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so parameter semantics is a non-issue and the baseline of 4 applies. The description correctly implies no required inputs by framing it as a status lookup keyed to 'today'.

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?

Names a specific verb+resource+scope: 'BZB daily trading-rewards status for swaps through BlazarFeeRouter', then enumerates the returned fields (today's dayId, posted days with totals and claim deadlines, daily cap, contract balance, scoring rules). This is clearly distinguishable from siblings like blazar_daily_claimable or blazar_build_claim, which it explicitly names.

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?

States when to use it precisely: 'find a dayId before blazar_daily_claimable or blazar_build_claim', giving both the ordering prerequisite and the downstream alternatives. It also constrains the environment ('Polygon only (chain 137)'). The only gap is an explicit when-not case (e.g., what to do for non-Polygon chains).

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