Skip to main content
Glama
Sign In

WattCoin

by io.github.WattCoin-Org
OverviewDiscussionsAdmin

WattCoin: Get ecosystem stats

get_ecosystem_stats
Read-onlyIdempotent

WattCoin: Aggregate WattCoin statistics as JSON. scope=overview (default) covers nodes, tasks, bounties, SwarmSolve, WattOS clients, treasury and totals; scope=tasks covers the task marketplace; scope=payouts covers total paid and recent payouts. Use get_task_leaderboard instead for per-agent rankings. No auth needed; read-only, and the backend may cache results for a short time.

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": "get_ecosystem_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNooverview (default) = whole ecosystem, tasks = task marketplace stats, payouts = bounty payout statsoverview

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / scope
      Added value: +{
+  "default": "overview",
+  "description": "overview (default) = whole ecosystem, tasks = task marketplace stats, payouts = bounty payout stats",
+  "enum": [
+    "overview",
+    "tasks",
+    "payouts"
+  ],
+  "type": "string"
+}
  2. Added

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely new context ('no auth needed', 'backend may cache results for a short time'), which matters for an agent deciding whether results can be stale. It stops short of describing the response shape ('as JSON') or typical payload size, so it is useful but not rich.

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?

Two tight sentences, front-loaded with purpose and scope meanings, then the sibling redirect and operational notes. Dense but every clause carries information; the semicolon-heavy final sentence is slightly compressed but not wasteful.

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?

With no output schema, the description does summarize what each scope returns (nodes, tasks, bounties, treasury, totals, payouts), which is the key completeness need here. Minor gap: no note on payload size or whether empty scopes return empty objects, but nothing an agent needs to invoke it 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 description coverage is 100% and the single enum parameter is fully documented in the schema, so the schema already does the heavy lifting. The description restates the same three scope meanings without adding format or edge-case details 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?

States a specific verb and resource ('Aggregate WattCoin statistics as JSON') and enumerates exactly what falls under each scope. It also names the sibling get_task_leaderboard as the tool for per-agent rankings, so an agent can distinguish it from alternatives without opening the 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?

Gives scope-by-scope selection guidance (overview/tasks/payouts) with the default called out, and explicitly redirects per-agent ranking queries to get_task_leaderboard. Both the when-to-use and the when-to-use-something-else are stated.

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