Skip to main content
Glama

Blazar Polygon plugin

BZB staking status and APR

blazar_staking_info
Read-onlyIdempotent

BZB single-sided staking (BlazarStakingRewards): status first (ACTIVE or REWARDS_ENDED with date), live APR from the reward rate, total staked, and optionally one account's stake, earned BZB and allowance. Use before building a stake, or to check rewards. 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_staking_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoOptional: include this address's stake, earned BZB and allowance.

Output Schema

NameRequiredDescriptionDefault
feeNo
lockNo
ownerNo
pausedNo
statusNo
accountNo
aprNoteNo
paidOutNo
contractNo
asOfBlockNo
aprPercentNo
rewardTokenNo
totalStakedNo
periodActiveNo
periodFinishNo
stakingTokenNo
rewardsActiveNo
rewardsPerDayNo
rewardAllocatedNo
contractBzbBalanceNo
rewardRatePerSecondNo
rewardsDurationSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered; the description adds genuine context beyond them: Polygon-only (chain 137), the ACTIVE/REWARDS_ENDED status model with an end date, and that APR is derived live from the reward rate rather than cached. It does not discuss failure behavior for an invalid or unstaked account, which is a minor remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense but well-ordered sentence set: identity and contract first, returned fields second, usage trigger third, chain constraint last. No filler and no restatement of the tool name or 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?

With an output schema present, return values need not be explained, yet the description still front-loads the key ones, and it adds the chain constraint and status enum an agent needs to interpret results. For a single-optional-parameter read tool this is close to complete, missing only guidance on the v2 alternative.

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 optional parameter is fully documented in the schema, including its address pattern. The description restates what the account parameter yields (stake, earned BZB, allowance) but adds no new semantics such as whether allowance is in BZB or the underlying token, so the baseline of 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?

The description names a specific resource (BZB single-sided staking via BlazarStakingRewards) and enumerates the exact fields returned: status, live APR, total staked, and optional per-account stake/earned/allowance. 'Single-sided' implicitly separates it from the v2 sibling, but it never names blazar_staking_v2_info as the alternative, so an agent must still infer the boundary.

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 before building a stake, or to check rewards' gives a concrete precondition tied to the sibling build tools. It stops short of stating when NOT to use it (e.g. when the v2 pool is the target), so the routing is clear but not exhaustive.

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