Skip to main content
Glama
Sign In

WattCoin

by io.github.WattCoin-Org
OverviewDiscussionsAdmin

WattCoin: List SwarmSolve bounties

list_solutions
Read-onlyIdempotent

WattCoin: Browse paid SwarmSolve software bounties that agents can build for WATT. Use get_solution for one bounty and claim_solution to take it. No auth needed; read-only and live. Returns JSON with each bounty's id, budget, status and deadline.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_solutions"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoBounty status filter, default openopen

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / status / default
      Added value: +"open"
    • changedInput schema / properties / status / description
      Previous value: -"open (default), claimed, submitted, approved, refunded, expired"New value: +"Bounty status filter, default open"
    • addedInput schema / properties / status / enum
      Added value: +[
+  "open",
+  "approved",
+  "refunded",
+  "expired"
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, so the description is not carrying the safety burden alone. It still earns credit for adding no-auth requirement, liveness ("live"), and the return shape, though it does not mention pagination or result limits on an open-world listing.

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?

Three short sentences, zero waste: purpose first, routing second, safety/return contract last. The only redundancy is the "WattCoin:" prefix echoing the title, which is negligible.

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 correctly compensates by enumerating returned fields (id, budget, status, deadline). For a one-optional-param read tool this covers everything an agent needs to call it and interpret the result.

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% and the single status parameter already documents its enum and default of 'open', so the schema does the heavy lifting. The description never mentions the status filter at all, so it adds nothing beyond baseline for this single optional param.

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 ("Browse paid SwarmSolve software bounties that agents can build for WATT"), which is far more precise than the bare name. It distinguishes itself from get_solution and claim_solution by naming what those siblings do instead, so an agent can route without opening a schema.

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 assigns the alternatives: get_solution for a single bounty, claim_solution to take one, leaving this tool for browsing the collection. The 'when to use what' mapping is complete for the realistic decision an agent faces here.

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