Skip to main content
Glama

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.

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description goes well beyond them: it names the log source, spells out the accounting rules (no minimum trade, no per-wallet cap, same-wallet round trips netted within 10 minutes), the listing/payout shape (top 50 listed, top 25 paid fixed shares of the daily cap) and the crucial caveat that results are estimates and only poster-posted winners are paid. These materially change how an agent should interpret and relay the output.

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?

Two sentences, front-loaded with the core action and source before the rules and the estimate caveat. Dense but nearly every clause carries operational weight; the rule list is long but each item affects how results should be read.

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?

With no output schema, the description still conveys what the leaderboard contains (top 50 listed, top 25 paid with fixed shares) and what the account option returns, plus the estimate-vs-payment boundary. An agent has enough to call it correctly and to explain the result without further sources.

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%, so both parameters (dayId, account) are already documented, including the UTC day formula and default. The description adds meaning mainly about what the optional account yields (rank, points, estimated BZB, points needed for a paid slot), which is return-value context rather than parameter semantics. Baseline 3 is appropriate.

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: 'Preview the BZB daily trading-rewards leaderboard for a UTC day', plus the data source (live BlazarFeeRouter AggregatedSwap logs) and the rule set used. That is far more than a restatement of the title. It does not name a sibling (e.g. blazar_daily_rewards or blazar_rank_earning) to contrast with, so it stops short of a 5.

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 'Preview' and by the explicit 'An ESTIMATE, not a payment: only poster-posted winners are paid', which tells the agent this is for inspection rather than claiming. However, no alternative tool is named and there is no explicit when-not guidance (e.g. 'use blazar_daily_rewards for final posted results').

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