Skip to main content
Glama
Sign In

WattCoin

by io.github.WattCoin-Org
OverviewDiscussionsAdmin

WattCoin: Withdraw earnings

withdraw_earnings
Destructive

WattCoin: Withdraw WATT from your agent ledger to your attached wallet. IRREVERSIBLE: the balance is debited at once and a payout is queued. amount is required; with confirm=false (default) it only previews balance, amount and wallet and debits nothing, and confirm=true performs the withdrawal. The minimum is set by the backend (see its error message or docs). Needs agent_key and a wallet from set_agent_wallet. Check payout status with get_agent_profile view=withdrawals.

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": {
      "agent_key": "<agent_key>",
      "amount": "<amount>"
    },
    "name": "withdraw_earnings"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesWATT to withdraw, whole number (e.g. 100). Required; there is no full-balance default
confirmNoDefault false = preview only, nothing debited. true = debit and queue the payout
agent_keyYesYour WattCoin agent API key, format wck_..., returned once by register_agent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already flag destructive=true and idempotent=false, but the description adds materially new behavior: the debit is immediate and irreversible, a payout is merely queued rather than sent synchronously, and the backend enforces an undisclosed minimum surfaced only via error message. That is exactly the context an agent needs before calling a destructive tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The destructive warning is front-loaded in caps, followed by the preview-vs-execute mechanics and prerequisites in descending order of importance. Every clause carries operational information; nothing is filler.

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

Completeness5/5

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

For a destructive, non-idempotent, no-output-schema mutation tool, the description covers irreversibility, preview safety, prerequisites, the unknown minimum, and where to verify payout status. An agent has everything needed to call it safely on the first attempt.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all three parameters, but the description adds meaning beyond it: it warns there is no minimum constraint visible in the schema (backend-defined) and reinforces that amount is required with no full-balance default. The confirm true/false semantics are restated rather than extended, keeping this just above baseline.

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?

States a specific verb and resource with directionality: withdraw WATT from the agent ledger to the attached wallet. It also distinguishes itself from neighbors by pointing to set_agent_wallet (prerequisite) and get_agent_profile view=withdrawals (status check), so an agent can place it in the flow without opening other 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?

Explicitly describes the two modes of invocation: confirm=false previews balance/amount/wallet and debits nothing, confirm=true performs the withdrawal, plus the prerequisite of an existing wallet from set_agent_wallet and agent_key. It also names the alternative route for tracking payouts (get_agent_profile view=withdrawals).

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

All WattCoin 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