Skip to main content
Glama

Blazar Polygon plugin

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
asOfNo
noteNo
rankedNo
verdictNo
contractsNo
statusKeyNo
deadRewardsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: data is derived from live reads only, every option carries one of five explicit status labels with a stated reason, deadRewards[] collects non-paying items, and the APR window is a trailing 24h. It does not mention freshness, caching, or failure behavior when a source is unavailable.

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?

The scope enumeration and the 'live reads only' qualifier are front-loaded where they matter most, and the chain restriction is placed as a closing constraint. The phrasing is dense and slightly telegraphic ('and why'), but no sentence is filler.

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?

An output schema exists, so the description need not explain return shape; the brief reference to deadRewards[] and the status vocabulary is enough to orient the agent. Combined with the chain restriction and the live-read guarantee, the definition is sufficient for a zero-required-parameter read tool, though a note on what happens when a source cannot be read would close the last gap.

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 there is only one optional parameter, so the schema already carries the burden and a 3 is the baseline. The description adds the trailing-24h framing for LP fee APR, which contextualizes why volume is read, but says nothing about includeVolume, its cost, or its default beyond what the schema states.

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?

The description opens with a specific verb and resource ('Rank BlazarForce earning options') and then enumerates the exact four instruments covered (BZB staking, BlazarSwap LP fee APR, daily trading rewards, staking v2), so an agent knows precisely what is being ranked. It falls short of a 5 because it never distinguishes itself from the plausibly overlapping sibling blazar_earn_strategies, leaving the agent to infer the boundary from the name alone.

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?

'Use instead of guessing yields' gives a clear positive trigger and implicitly rules out ad-hoc yield estimation, and 'Polygon only (chain 137)' states a hard precondition before the call. There is no explicit when-not or named alternative among the sibling tools, so it stops short of full routing guidance.

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