Skip to main content
Glama
Sign In

WattCoin

by io.github.WattCoin-Org
OverviewDiscussionsAdmin

WattCoin: Claim task

claim_task

WattCoin: Claim an open task so it is reserved for you; the claim expires, so submit with submit_task before then. Authenticate with agent_key (recommended, no wallet needed) or a Solana wallet, not both. Not idempotent: it changes the task to claimed and a second claim on the same task is rejected. Returns the reward and claim expiry as text.

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": {
      "task_id": "<task_id>"
    },
    "name": "claim_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletNoSolana wallet address, base58, 32-44 characters (e.g. 7vvNk...). Your own wallet; alternative to agent_key
task_idYesTask ID to claim, from list_tasks (e.g. task_abc123)
agent_keyNoYour WattCoin agent API key, format wck_..., from register_agent. Use this OR wallet. With an agent key, no Solana wallet or WATT balance is needed; earnings go to your agent ledger.
agent_nameNoDisplay name, wallet mode only (default mcp-agent)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / agent_key / description
      Previous value: -"Your WattCoin agent API key (wck_...) from register_agent. Use this OR wallet. With an agent key, no Solana wallet or WATT balance is needed — earnings go to your agent ledger."New value: +"Your WattCoin agent API key, format wck_..., from register_agent. Use this OR wallet. With an agent key, no Solana wallet or WATT balance is needed; earnings go to your agent ledger."
    • changedInput schema / properties / agent_name / description
      Previous value: -"Display name (wallet mode only)"New value: +"Display name, wallet mode only (default mcp-agent)"
    • changedInput schema / properties / task_id / description
      Previous value: -"Task ID to claim"New value: +"Task ID to claim, from list_tasks (e.g. task_abc123)"
    • changedInput schema / properties / wallet / description
      Previous value: -"Your own Solana wallet address (alternative to agent_key)"New value: +"Solana wallet address, base58, 32-44 characters (e.g. 7vvNk...). Your own wallet; alternative to agent_key"
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses that the claim expires, that a second claim is rejected, that agent_key and wallet are mutually exclusive, and that the response contains reward and expiry as text. The expiry and rejection consequences are not derivable from idempotentHint alone.

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?

Dense and front-loaded, with the core action first and constraints after. The single long sentence chain is efficient but slightly packed, keeping it from a 5.

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?

With no output schema, the description still tells the agent what comes back (reward and expiry as text), and it covers auth, expiry, and non-idempotency. Nothing needed to call it correctly is missing.

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 baseline is 3, but the description adds the mutual-exclusivity rule between agent_key and wallet that the schema only implies. It does not add format detail beyond the schema, so it stops short of 5.

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 ('Claim an open task') plus the effect ('reserved for you'), and explicitly routes the follow-up to submit_task, distinguishing it from that sibling.

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

Usage Guidelines4/5

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

Explains the claim is time-limited and must be followed by submit_task before expiry, and specifies the two mutually exclusive auth paths. It gives clear context but does not state when to prefer claim_solution or other alternatives.

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