Skip to main content
Glama
Sign In

WattCoin

by io.github.WattCoin-Org
OverviewDiscussionsAdmin

WattCoin: Set agent payout wallet

set_agent_wallet
DestructiveIdempotent

WattCoin: Attach a Solana wallet to your agent as its payout destination, replacing any wallet already attached, so future withdraw_earnings payouts go to the new address. Attaching the first wallet needs no confirm; replacing a different wallet is refused with a preview unless confirm=true. Needs agent_key; the backend rejects reserved or restricted wallets. Setting the same wallet again changes nothing. Returns JSON with the wallet and the previous one.

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>",
      "wallet": "<wallet>"
    },
    "name": "set_agent_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYesSolana wallet address, base58, 32-44 characters (e.g. 7vvNk...). The new payout wallet
confirmNoDefault false. Must be true to replace a different wallet that is already attached
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.7/5.0
Behavior5/5

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

Annotations declare destructive/openWorld/idempotent, and the description goes further by explaining exactly how destruction is gated (preview refusal, confirm=true) and which wallets are refused server-side. It also discloses that the response includes both the new and previous wallet, matching the idempotentHint with 'setting the same wallet again changes nothing'.

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?

Front-loaded with purpose and effect, then the confirm gate, then prerequisites and the return shape. Every sentence carries distinct information with no padding.

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?

Despite no output schema, the description specifies the JSON return (wallet and previous wallet), the auth requirement, the confirm gate, and the no-op case. Nothing an agent needs to call this correctly is missing.

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 coverage is 100%, so all three parameters (wallet format, confirm default/semantics, agent_key format) are already documented in the schema. The description reinforces confirm's gating behavior but adds no new parameter-level detail beyond what the schema states, so the baseline 3 applies.

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 (attach a Solana wallet as payout destination) plus the downstream effect (future withdraw_earnings payouts). It also distinguishes this from the sibling withdraw_earnings by naming that tool as the consumer rather than the same operation.

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 states the two cases: first attach needs no confirm, while replacing a different wallet is refused with a preview unless confirm=true. It also states the prerequisite (agent_key) and the backend's rejection of reserved or restricted wallets, and notes that setting the same wallet is a no-op.

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