Skip to main content
Glama

Blazar Polygon plugin

Build stake / withdraw / claim / exit

blazar_build_stake
Read-only

One call for BZB staking: ordered txs[] (exact approve if needed, then stake / withdraw / claim / exit), a summary per tx, a simulation, and warnings (e.g. REWARDS_ENDED, NOTHING_TO_CLAIM). No lock, no fee. Returns UNSIGNED txs. Polygon only (chain 137).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>",
      "from": "<from>"
    },
    "name": "blazar_build_stake"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromYesAddress that will sign and send the txs. Required: used for allowance checks, simulation and nonce.
actionYesstake: deposit BZB. withdraw: take back some. claim: collect rewards only. exit: withdraw all + claim.
amountNoBZB in HUMAN units, e.g. "250". Required for stake and withdraw.
amountIsBaseUnitsNoIf true, amount is in base units (wei for 18-decimal tokens; 6 decimals for USDC). Default false.

Output Schema

NameRequiredDescriptionDefault
txsYesSign and send in order.
fromNo
nextNo
batchNoEIP-5792 wallet_sendCalls request with the same calls (smart wallets).
quoteNo
actionYes
guardsNo
safetyNo
chainIdNo137 Polygon, 8453 Base, 1 Ethereum. BlazarForce builds are always 137.
detailsNo
signingNo
summaryYes
warningsYes
routeGuideNo
simulationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag readOnlyHint=true, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered; the description adds real behavior on top. It discloses that approvals are inserted order-exactly, that a simulation and per-tx summary are produced, that warnings such as REWARDS_ENDED and NOTHING_TO_CLAIM can surface, and that only unsigned txs are returned for the caller to sign. It does not say what the caller must do after signing or whether repeated calls differ (idempotentHint=false is never explained).

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?

A single dense passage with the core purpose front-loaded and no filler sentences. Slight redundancy: it enumerates return contents (summaries, simulation, warnings) although an output schema already exists, making part of the wording non-essential.

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?

For a 4-parameter builder with full schema coverage and an output schema, the description covers the essentials an agent needs: chain restriction, no lock or fee, unsigned-tx handoff, and expected warnings. Missing only the routing relationship to the neighboring claim and staking-v2 builders and any post-signing expectation.

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 description coverage is 100%, so every parameter is already documented in the schema, including the action enum definitions and the human-units vs base-units distinction. The description reinforces that amount is only meaningful for stake/withdraw but adds no new format or constraint detail. Baseline 3 applies when the schema carries the parameter burden.

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?

Names a specific resource and verb: one call that builds for BZB staking the ordered txs (approve, then stake/withdraw/claim/exit). The four supported actions and the 'returns UNSIGNED txs' outcome make the tool's job unambiguous. It stops short of naming a sibling (e.g. blazar_build_claim or blazar_build_staking_v2), so an agent must infer differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is implied rather than stated: 'Polygon only (chain 137)' and 'No lock, no fee' tell the agent when this applies, and the action list hints at the four cases. There is no explicit when-not or routing to blazar_build_claim (claim-only) or blazar_build_staking_v2, both of which plausibly overlap.

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