Skip to main content
Glama
Sign In

WattCoin

by io.github.WattCoin-Org
OverviewDiscussionsAdmin

WattCoin: Browse skills marketplace

browse_marketplace
Read-onlyIdempotent

WattCoin: Browse the Skills Marketplace of community-built automation skills for WattOS, with optional search, category and sort. Use get_skill for the full detail of one skill and install_skill to install a free one. No auth needed; read-only and live. Returns a text list with name, version, author, price, install count, rating and category.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1
sortNoSort order: newest (default), installs or ratingnewest
limitNoResults per page, 1-50, default 20
searchNoSearch text matched against name, description and author (e.g. pdf)
categoryNoCategory filter; omit for all categories

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"productivity, development, system, finance, communication, data, media, other"New value: +"Category filter; omit for all categories"
    • addedInput schema / properties / category / enum
      Added value: +[
+  "productivity",
+  "development",
+  "system",
+  "finance",
+  "communication",
+  "data",
+  "media",
+  "other"
+]
    • addedInput schema / properties / limit / default
      Added value: +20
    • changedInput schema / properties / limit / description
      Previous value: -"Results per page (default 20, max 50)"New value: +"Results per page, 1-50, default 20"
    • changedInput schema / properties / limit / maximum
      Previous value: -9007199254740991New value: +50
    • changedInput schema / properties / limit / minimum
      Previous value: --9007199254740991New value: +1
    • addedInput schema / properties / page / default
      Added value: +1
    • changedInput schema / properties / page / description
      Previous value: -"Page number (default 1)"New value: +"Page number, starting at 1"
    • changedInput schema / properties / page / minimum
      Previous value: --9007199254740991New value: +1
    • changedInput schema / properties / search / description
      Previous value: -"Search by name, description, or author"New value: +"Search text matched against name, description and author (e.g. pdf)"
    • addedInput schema / properties / sort / default
      Added value: +"newest"
    • changedInput schema / properties / sort / description
      Previous value: -"newest (default), installs, rating"New value: +"Sort order: newest (default), installs or rating"
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "newest",
+  "installs",
+  "rating"
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld and destructive=false, and the description reinforces this with 'No auth needed; read-only and live.' Because no output schema exists, the description's enumeration of returned fields (name, version, author, price, install count, rating, category) is genuinely additive; only pagination/total-count behavior is left unstated.

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 tight sentences ordered by importance: what it is, what alternatives exist, then operational behavior and return shape. The 'WattCoin:' prefix is the only mild redundancy with the title, but nothing else is wasted.

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?

For a 5-param, zero-required read tool with rich annotations and no output schema, the description covers auth, safety, alternatives and return fields. The remaining gap is pagination/ordering of results across pages, which the description leaves entirely to the schema defaults.

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%, including enum values and defaults for sort, category, page and limit, so the schema carries parameter meaning. The description only echoes 'optional search, category and sort' and says nothing about page/limit semantics, so it adds little beyond the schema — a baseline 3.

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 (Browse) and resource (Skills Marketplace of community-built automation skills for WattOS) plus the supported filters. It is immediately distinguishable from get_skill (single-skill detail) and install_skill (mutation), which are named explicitly.

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 routes the agent: 'Use get_skill for the full detail of one skill and install_skill to install a free one.' It also states the context precondition (no auth needed) so an agent knows it can call this before registering or authenticating.

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