Skip to main content
Glama

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.

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.

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 declare readOnly, non-destructive, non-idempotent, open-world, but the description adds real behavior: the txs are ordered, an exact approve is auto-inserted when needed, a simulation and per-tx summary are included, and named warnings (REWARDS_ENDED, NOTHING_TO_CLAIM) can appear. It also states there is no lock and no fee, and that unsigned txs are returned. It stops short of describing ordering/expiry requirements for signing or any 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?

A single dense sentence front-loads the core purpose before the output and warning details. It is efficient, though compressed notation like 'txs[]' and 'exact approve' assumes familiarity and would read better split into two short clauses.

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 correctly states the return shape (unsigned txs) and previews the summary, simulation, and warnings, which is what an agent needs to know before calling. Gaps remain around whether txs must be signed and sent in order and any time-sensitivity of the built bundle.

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%, with units, enum meanings, and the from-address purpose already documented, so the baseline is 3. The description's only added semantic value is the note that the approve step is exact, which concerns the generated output rather than the inputs.

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 a concrete verb-and-resource: one call that builds an ordered tx bundle for four BZB staking actions (stake/withdraw/claim/exit), with approve prepended when needed. It clearly distinguishes itself from generic build tools by scoping to BZB staking, but it never says how it differs from the sibling blazar_build_staking_v2 or blazar_build_claim, which overlap on claim.

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?

The action enum carries implicit usage guidance, and the description implies you use this whenever you want a staking transaction bundle. There is no explicit when-to-use versus when-not guidance, and with siblings like blazar_build_staking_v2 and blazar_build_claim present, the agent is left to infer which builder is appropriate.

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