Skip to main content
Glama

Blazar Polygon plugin

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
feeNo
asOfNo
lockNo
ownerNo
alertsNo
pausedNo
statusNo
gasNoteNo
versionNo
contractNo
minStakeNo
positionNo
asOfBlockNo
totalStakedNo
pendingOwnerNo
rewardTokensNo
stakingTokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the exact contract address, the chain restriction, that status/alerts are returned first, and that the account position is only included when the optional address is supplied.

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 contract identity and chain constraint are front-loaded, and the return inventory is packed into a single dense sentence. The long enumeration of returned fields is somewhat list-heavy but each item is informative, and no sentence is pure 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?

With one optional parameter and a declared output schema, the definition supplies everything needed to call it correctly: chain, address, optional account behavior, and where it sits relative to the build tool. The main omission is how it relates to the sibling v1 info tool, which would help an agent choose between them.

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?

There is a single optional parameter and schema coverage is 100%, so the schema already documents the address pattern and its purpose. The description restates the effect of supplying it ('optionally one account's stake, share and claimable rewards') but adds no format or edge-case detail beyond the schema, which is the expected baseline at full coverage.

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 concrete contract (BlazarMultiRewardStaking, staking v2, BZB, up to 5 reward tokens, no lock) and enumerates what the read returns: status, minStake, totalStaked, per-token rates, 24h/7d emissions, APR, and optional account position. It implicitly separates itself from the v1 reader via 'staking v2' and from blazar_build_staking_v2 by being the pre-build read, though it never states the contrast with blazar_staking_info explicitly.

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?

It gives an explicit sequencing instruction ('Use before blazar_build_staking_v2') and a hard constraint ('Polygon only (chain 137)'), which tells the agent both when to reach for it and on which chain. There is no when-not guidance, e.g. what to use if the user is on another chain or is staking a non-BZB asset.

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