Skip to main content
Glama

Blazar Polygon plugin

Build staking v2: stake / withdraw / claim / exit (gas-padded)

blazar_build_staking_v2
Read-only

One call for staking v2: ordered txs[] for stake (exact approve + stake), withdraw, claimAll, claimMany (defaults to only tokens with rewards), exit or emergencyWithdraw, each with a summary, a simulation, warnings, and a gas limit. withdraw / exit / emergencyWithdraw / claimAll carry gas = max(estimateGas x 1.25, 1.1M) because a cold exit can use ~885k. 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_staking_v2"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromYesAddress that will sign and send the txs. Required: used for allowance checks, simulation and nonce.
actionYesstake: deposit. withdraw: take back some (the rest must stay >= minStake or be 0). claimAll: every reward token (all-or-nothing). claimMany: chosen tokens (default: tokens with rewards). exit: withdraw all + claim all. emergencyWithdraw: last resort, principal only, rewards stay claimable.
amountNoStaking-token amount in HUMAN units, e.g. "250" = 250 BZB. Required for stake and withdraw.
tokensNoclaimMany only: reward token addresses. Default: every token where earned > 0.
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?

Goes well beyond the annotations by disclosing the return payload shape (summary, simulation, warnings, gas limit) and the gas-padding rule (max(estimateGas x 1.25, 1.1M) with a ~885k cold-exit justification). 'Returns UNSIGNED txs' is consistent with readOnlyHint=true and destructiveHint=false since nothing is broadcast. Not stated: whether the caller needs any approval/signing prerequisites or rate limits.

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?

Two dense sentences, front-loaded with 'One call for staking v2' and the returned artifact, with the gas rule and chain restriction after. The action list is somewhat redundant against the schema enum, but the padding rationale (~885k cold exit) earns its space.

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, annotations, and full parameter coverage, the description only needs to add what structured fields cannot: the unsigned-transaction contract, the gas-padding policy, and the chain restriction, all of which it supplies. A brief note on prerequisites (allowance/approval state, nonce handling implied by 'from') would close the remaining gap.

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, and the description mostly restates the action list and claimMany default rather than adding new meaning. The one genuinely additive detail is that stake bundles an 'exact approve + stake', which explains the approve requirement implicitly attached to the from/amount parameters.

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?

States a specific verb+resource: builds ordered unsigned staking-v2 transactions, and enumerates exactly which actions (stake, withdraw, claimAll, claimMany, exit, emergencyWithdraw) it covers. It is clear what an agent gets back ('Returns UNSIGNED txs'), but it never names how it differs from siblings such as blazar_build_stake or blazar_staking_v2_info, leaving the v1-vs-v2 boundary implicit.

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 is implied by the action enumeration and by the 'Polygon only (chain 137)' constraint, which functions as a de facto when-not condition. There is no explicit guidance on when to pick this over the single-action siblings (blazar_build_stake / blazar_build_claim) or over the read-only info tool, so the agent must infer routing.

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