Skip to main content
Glama
Sign In

Wicked MCP

by io.github.WickedAPI
OverviewDiscussionsAdmin

reputation_withdraw

Destructive

[Wicked Reputation] Pay out every unbonding stake whose cooldown has elapsed, in one on-chain transfer to your wallet. Safe to retry if a payout fails. Needs a signed nonce.

Use when your unbonding cooldown has elapsed and you want every matured stake paid out to your wallet. Not for starting the unbonding (use reputation_unstake).

Behavior: DESTRUCTIVE and not reversible; confirm intent before calling.

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>",
      "nonce": "<nonce>",
      "signature": "<signature>"
    },
    "name": "reputation_withdraw"
  }
}

Input Schema

NameRequiredDescriptionDefault
nonceYesNonce from a FRESH reputation_get_nonce call.
walletYesYour 0x wallet address on Base.
signatureYes0x-prefixed ECDSA signature (EIP-191) over that nonce's message, from YOUR wallet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so 'DESTRUCTIVE and not reversible' largely restates them, but the description adds real value beyond annotations: the payout is batched into one transfer, retry after a failed payout is safe, and a signed nonce is required. It does not describe what is returned (amounts, tx hash), which is a minor gap for a destructive tool with no output schema.

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?

Front-loaded with the core action, then usage, then behavior, with no wasted filler. There is mild redundancy between the opening sentence and the 'Use when' sentence, which restates the cooldown-elapsed condition.

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?

All three required parameters are documented, the destructive/irreversible behavior and sibling alternative are covered, and annotations carry the safety profile. Only the absence of any return-value context (payout amount, transaction reference) keeps it shy of complete.

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 the schema already documents wallet, nonce, and signature in detail, including the 'FRESH' nonce constraint. The description only echoes that a signed nonce is needed, adding no per-parameter meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb and resource: pays out matured unbonding stakes in a single on-chain transfer. It also explicitly distinguishes itself from reputation_unstake, so an agent can route between the two without inspecting schemas.

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

Usage Guidelines5/5

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

States the triggering condition (cooldown elapsed, matured stakes exist) and the exclusion with the named alternative ('Not for starting the unbonding (use reputation_unstake)'). Both the when and when-not are explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Wicked MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources