Skip to main content
Glama

Staking v2 (multi-reward): status, rates, APR, position

blazar_staking_v2_info
Read-onlyIdempotent

BlazarMultiRewardStaking (staking v2: stake BZB, earn up to 5 reward tokens, no lock). Live at 0x4222bFF08cc9D42cd3311033a4882314DfE19615. One call returns status/alerts first, minStake, totalStaked, every reward token with per-second rate, next-24h and next-7d emission from the run curves, APR (token-denominated or Chainlink USD when available), run schedule, and optionally one account's stake, share and claimable rewards. Use before blazar_build_staking_v2.

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

Input Schema

NameRequiredDescriptionDefault
accountNoOptional: include this address's stake, pool share and claimable rewards.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), so the description's job is to add context — and it does, by disclosing the deployed address, that results are ordered with status/alerts first, that emission figures come from run curves, and that USD APR depends on Chainlink availability. It says nothing about rate limits or failure modes, but that is a minor gap given strong annotation coverage.

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?

Identity, address, and return payload are front-loaded in a tight sequence with no filler sentences. It is information-dense to the point of being a long run-on list, but every clause earns its place and nothing is repeated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

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

There is no output schema, so the description must carry the return-value burden — and it enumerates status/alerts, minStake, totalStaked, per-token rates, 24h/7d emissions, APR, run schedule, and optional position data. For a one-optional-parameter read tool, nothing an agent needs in order to call it correctly is missing.

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 'account' parameter is fully documented there, so the description only needs to reinforce it. It does so by restating that supplying an account yields stake, pool share and claimable rewards, but adds no format, default, or behavioral nuance beyond the schema — the baseline 3 is appropriate.

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?

Names the contract (BlazarMultiRewardStaking), states the stake asset (BZB), the reward model (up to 5 tokens, no lock), and enumerates exactly what the single call returns. The 'v2: multi-reward' framing lets an agent distinguish it from the sibling blazar_staking_info without opening either schema.

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?

Explicitly sequences the tool: 'Use before blazar_build_staking_v2', which tells the agent this is the read/status step preceding the build step. It gives no when-not-to-use condition or guidance versus blazar_staking_info, but the primary placement guidance is unambiguous.

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