Skip to main content
Glama

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.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered structurally. The description adds non-obvious content scope (claim deadlines, daily cap, contract balance, scoring rules), but says nothing about data freshness, caching, or whether 'recently posted days' is bounded.

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 resource and its returned fields, followed by the usage/routing sentence. The field list is dense but each item carries distinct information; 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.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a no-parameter read tool with no output schema, so the description must carry the return-value burden — and it does, enumerating the fields an agent will receive. The only gap is operational behavior (staleness, whether the day list is truncated), which is minor for a status read.

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, which is the baseline-4 case: there is nothing for the description to disambiguate. The description correctly implies a parameterless snapshot call and does not invent input requirements.

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?

The description states a specific resource (BZB daily trading-rewards status via BlazarFeeRouter) and enumerates the concrete outputs: today's dayId, recently posted days with totals and claim deadlines, daily cap, contract balance, and scoring rules. This is far beyond restating the title, and it distinguishes the tool from siblings that act on a dayId rather than report it.

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 gives explicit routing: use this to find a dayId before calling blazar_daily_claimable or blazar_build_claim, naming both alternatives and the precondition that selects them. It stops short of stating when not to use it (e.g., if the caller already holds a dayId), so a 4 rather than a 5.

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