Skip to main content
Glama

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.

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.

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 this a read-only, idempotent, non-destructive call, so the safety profile is covered. The description adds genuinely useful behavior — the ACTIVE/REWARDS_ENDED state model with a date, and that APR is derived live from the reward rate rather than cached — but says nothing about freshness guarantees, chain scope, or failure modes for an invalid address.

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?

Dense and front-loaded: the returned fields come first, followed by the usage cue, with no filler. The first sentence is packed with parentheticals (contract name, status states) but every clause carries information an agent needs.

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 no output schema, the description correctly takes on the burden of enumerating return values — status, APR, total staked, and the optional account triple — which is enough to decide whether to call it. Minor gaps remain around which network the data comes from and how an unknown address is handled.

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 parameter is fully documented, so the schema does the work. The description's "optionally one account's stake, earned BZB and allowance" restates the schema description rather than adding new meaning such as whether omitting it still returns global totals.

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 the specific resource and contract (BZB single-sided staking, BlazarStakingRewards) and enumerates exactly what it reports: status, live APR, total staked, and optional per-account stake/earned/allowance. The contract reference implicitly separates it from the blazar_staking_v2_info sibling, but it never states that distinction outright.

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 two concrete invocation triggers tied to real workflows. It stops short of exclusions — most notably it does not say when to prefer the v2 staking info sibling over this one.

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