Skip to main content
Glama
Sign In

WattCoin

by io.github.WattCoin-Org
OverviewDiscussionsAdmin

CoinLoader/BotAppStore: List bots

list_products
Read-onlyIdempotent

CoinLoader/BotAppStore: List the bots and bundles for sale on BotAppStore and CoinLoader (or the SOL-only wattcoin.org bots with site=wattcoin). Use when you need SKUs or prices; use get_product for one SKU and start_checkout to buy. No auth needed; read-only, live, creates no order. Returns JSON with sku, name, USD price, payment methods, summary and page URL for live, purchasable items only.

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_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoStore: botappstore, coinloader, or wattcoin (wattcoin.org bots, SOL only). Omit to list BotAppStore and CoinLoader together
storefrontNoAlias of site for botappstore or coinloader; site wins if both are given

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / site / description
      Previous value: -"botappstore (default), coinloader, or wattcoin (wattcoin.org bots, SOL only); omit for BotAppStore and CoinLoader"New value: +"Store: botappstore, coinloader, or wattcoin (wattcoin.org bots, SOL only). Omit to list BotAppStore and CoinLoader together"
    • changedInput schema / properties / storefront / description
      Previous value: -"Alias of site for botappstore / coinloader"New value: +"Alias of site for botappstore or coinloader; site wins if both are given"
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds genuinely new context: no auth required, results are live, no order is created, and only live purchasable items are returned. The return field list is a bonus, though serving/pagination and result size are not addressed.

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?

Three tight, front-loaded sentences: purpose, selection guidance, then operational facts. The leading "CoinLoader/BotAppStore:" prefix mildly duplicates the title but costs little.

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?

For a zero-required-param read tool with no output schema, everything an agent needs is present: auth requirements, what is filtered out, the shape of returned JSON, and which sibling to pick instead.

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% and both parameters are fully enumerated with defaults and the site-wins precedence rule, so the description adds little beyond restating that site=wattcoin means SOL-only wattcoin.org bots. Baseline 3 applies when the schema carries the semantics.

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 ("List the bots and bundles for sale") plus the two storefronts and the special wattcoin scope. It is clearly distinguishable from get_product and start_checkout, which are named.

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 says when to use it ("when you need SKUs or prices") and routes to alternatives: get_product for a single SKU, start_checkout to buy. The site=wattcoin variant adds a further selection rule.

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