Skip to main content
Glama

Blazar Polygon plugin

Trading-rewards leaderboard preview (estimate)

blazar_trading_rewards_preview
Read-onlyIdempotent

Preview the BZB daily trading-rewards leaderboard for a UTC day from live BlazarFeeRouter AggregatedSwap logs, using the swap-desk rules: no minimum trade, no per-wallet cap, same-wallet round trips within 10 minutes netted, top 50 listed, top 25 paid fixed shares of the daily cap. Optional account shows its rank, points, estimated BZB and points needed for a paid slot. An ESTIMATE, not a payment: only poster-posted winners are paid. 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_trading_rewards_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayIdNoUTC day number = floor(unix/86400). Default: today.
accountNoOptional: show this address's rank, points and gap to a paid slot.

Output Schema

NameRequiredDescriptionDefault
dateNo
boardNo
dayIdNo
rulesNo
alertsNo
scannedNo
tradersNo
dailyCapBzbNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations cover read-only/idempotent safety, and the description adds genuinely new behavioral context: data is computed from live on-chain logs, the exact scoring rules (no minimum, no cap, 10-minute round-trip netting), payout structure (top 50 listed, top 25 paid fixed shares), the estimate-vs-actual distinction, and the chain restriction. This is far more than the annotations disclose.

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?

Purpose and data source are front-loaded in the first clause, followed by rules and caveats. It is one long run-on sentence with dense rule enumeration, but nearly every clause (netting rule, top 50/25, estimate caveat, chain 137) carries decision-relevant information.

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?

An output schema exists, so return shape need not be described. Combined with full schema coverage, disclosed scoring rules, payout structure, liveness of the data source, and the estimate caveat, an agent has everything needed to call this correctly and interpret the result.

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 both parameters are fully documented in the schema including the default 'today' and the address pattern. The description echoes the same meaning (dayId = UTC day, account shows rank/points/estimated BZB/gap) without adding syntax or format detail beyond the schema, so it meets the baseline rather than exceeding it.

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 ('Preview the BZB daily trading-rewards leaderboard for a UTC day') plus data source (live BlazarFeeRouter AggregatedSwap logs) and scope (chain 137 only). An agent immediately knows this is a read-only estimation tool for a specific leaderboard, distinct from claim/build tools in the sibling set.

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?

Clear context is given: use it to preview/estimate what a day's leaderboard and payout looks like, including a specific account's gap to a paid slot. The line 'An ESTIMATE, not a payment: only poster-posted winners are paid' implicitly routes the agent elsewhere for actual claiming, but no sibling is named explicitly (e.g. blazar_daily_claimable or blazar_rank_earning), leaving the alternative to inference.

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