Skip to main content
Glama

Rank earning options; flag dead rewards

blazar_rank_earning
Read-onlyIdempotent

Rank BlazarForce earning options from live reads only: BZB staking, BlazarSwap LP fee APR (trailing 24h), daily trading rewards, staking v2. Each has status LIVE / UNPROVEN / IDLE / DEAD / NOT_DEPLOYED and why. deadRewards[] lists anything that pays nothing now. Use instead of guessing yields.

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_rank_earning"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeVolumeNoRead 24h pool volume for LP fee APR (default true, ~2-5 s).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and open-world, yet the description adds real behavioral context: data comes from 'live reads only', the LP APR is a trailing 24h figure, and each option carries one of five named statuses plus a reason. It also discloses the deadRewards[] return field, which matters since there is no output schema. It stops short of explaining cost/latency or what 'why' looks like.

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 tightly packed sentences, front-loaded with the action and scope, with no filler. The dense jargon and status list make it slightly harder to scan than a cleaner structure would, but nothing is wasted.

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?

Given no output schema, the description carries the return-shape burden and does so by naming deadRewards[] and the status vocabulary. It is nearly complete for a ranking tool, though it does not say whether numeric yields/APRs are returned or what fields accompany each status.

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 the single includeVolume parameter is fully documented in the schema, including its default and 2-5 s cost. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 ('Rank BlazarForce earning options') and enumerates the four covered categories (BZB staking, BlazarSwap LP fee APR, daily trading rewards, staking v2), which is enough to tell it apart from build/claim/quote siblings. It does not name a sibling explicitly, so it falls short of 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?

'Use instead of guessing yields' gives an implied use case, but there is no explicit when-not guidance and no named alternative (e.g. blazar_compare_venues or blazar_earn_strategies) for the agent to route between. Usage is inferable rather than stated.

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