Skip to main content
Glama

Build: solver stake and balance

build_prediction_account
Read-only

Deposit or withdraw solver stake (backs the 1% bonds of your proposals), or withdraw your balance (dispute winnings and returned bonds).

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": {
      "wallet": "<wallet>",
      "action": "<action>"
    },
    "name": "build_prediction_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
walletYesthe agent's wallet address — the one that will sign and send the calls
amountUsdcNoUSDC, for deposit_stake / withdraw_stake, as a decimal string, e.g. "25" or "0.5"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

The description adds real domain context (what stake backs, where balance comes from), but the verbs 'deposit or withdraw' read as state-changing while the annotations declare readOnlyHint=true. The description never explains the reconciliation — that this is a build tool returning unsigned calls for the wallet to sign — leaving the agent to infer it from the 'build_' prefix and the wallet parameter text. No mention of gas, approvals, or what the response contains.

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 front-loaded sentence with no filler; the action list comes first and the parentheticals explain the jargon. Nested parentheses and terms like 'solver stake' and 'bonds' cost some immediate legibility, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and an annotation set that implies the opposite of the verbs used, the description should clarify the call-building lifecycle and what the agent gets back, as well as whether amountUsdc is mandatory per action. It covers the three actions but leaves the tool's actual behavior and return value under-specified.

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 67%: the wallet field is documented and the action enum is self-explanatory, while amountUsdc is described in the schema as applying only to deposit_stake/withdraw_stake. The description adds no meaning beyond the schema — it doesn't restate that an amount is required for stake actions but not for withdraw_balance — so the baseline of 3 applies.

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 specific verbs and resources: deposit/withdraw solver stake, and withdraw balance, each with a short economic gloss (backs the 1% bonds of proposals; dispute winnings and returned bonds). An agent can tell this is the account/stake-funding tool of the build_* family. It stops short of explicitly contrasting with siblings such as build_prediction_trade, which keeps it from a 5.

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 three action values are implicitly mapped to their purposes (staking vs. claiming balance), which gives useful context for choosing among them. However, there is no explicit when-to-use/when-not guidance, no prerequisites such as USDC approval or required amount for stake actions, and no mention of what to call instead when the user simply wants to view stake or portfolio.

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