Skip to main content
Glama

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.

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.

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?

The description adds real behavior beyond the annotations: it returns UNSIGNED txs (consistent with readOnlyHint=true), each carrying a summary, simulation, warnings and gas limit, and it explains the gas padding formula max(estimateGas x 1.25, 1.1M) with the rationale of a ~885k cold exit. It does not disclose failure modes (e.g. what happens if simulation fails, or whether approve and stake can be submitted separately).

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 with the action list front-loaded and the gas-padding caveat second; essentially nothing is wasted. The second sentence is a run-on that buries the return statement ("Returns UNSIGNED txs") at the very end, which slightly hurts scannability.

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 steps in to describe the return shape (per-action txs each with summary, simulation, warnings, gas limit) and flags that txs are unsigned. For a multi-mode transaction builder the remaining gaps are error/failure behavior and whether approve must be broadcast before stake.

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 already carries its own semantics (human units, amountIsBaseUnits, token list defaults, action enum meanings). The description restates a few of these, notably the claimMany default, but adds no syntax or format detail the schema lacks. Baseline 3 applies when the schema does the heavy lifting.

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 opens with a specific verb and resource ("One call for staking v2") and enumerates the six supported actions, so an agent knows exactly what the tool produces: ordered unsigned txs. It does not explicitly contrast itself with the v1-looking siblings blazar_build_stake / blazar_build_claim, leaving that differentiation to the name and title.

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 by the action list (e.g. "emergencyWithdraw: last resort", withdraw requiring the remainder to stay >= minStake or be 0), which helps pick an action. However, there is no explicit when-to-use-this-vs-alternatives routing, such as why to call this instead of the sibling blazar_build_stake or when to consult blazar_staking_v2_info first.

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