Skip to main content
Glama
Sign In

WattCoin

by io.github.WattCoin-Org
OverviewDiscussionsAdmin

CoinLoader/BotAppStore: Get bot

get_product
Read-onlyIdempotent

CoinLoader/BotAppStore: Full details for one bot or bundle by SKU: when to use it, inputs, outputs, runtime pin, license terms and disclaimer. Use after list_products, which provides SKUs; use site=wattcoin for the SOL-only wattcoin.org view. No auth needed; read-only and live. Returns JSON, or an error if the SKU is not live.

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": {
      "sku": "<sku>"
    },
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuYesProduct or bundle SKU from list_products (e.g. mill-cert-matcher), case-insensitive
siteNoStore: botappstore, coinloader, or wattcoin (wattcoin.org bots, SOL only). Omit to return every storefront's entry for the SKU

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 to list every storefront's entry"New value: +"Store: botappstore, coinloader, or wattcoin (wattcoin.org bots, SOL only). Omit to return every storefront's entry for the SKU"
    • changedInput schema / properties / sku / description
      Previous value: -"Product or bundle SKU, e.g. mill-cert-matcher"New value: +"Product or bundle SKU from list_products (e.g. mill-cert-matcher), case-insensitive"
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description adds genuinely new facts: no auth required, data is live, and a non-live SKU yields an error instead of a result. It stops short of describing multi-storefront merge behavior when site is omitted, which is the one remaining behavioral gap.

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?

The resource and scope are front-loaded in the first clause, and every subsequent sentence contributes a prerequisite, a routing rule, or a return/error note. Slightly dense — the list of returned fields is packed into one long clause — but nothing is wasted.

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 summarizing the return payload (

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 schema already documents that sku is case-insensitive and comes from list_products, and that wattcoin is SOL-only. The description's mention of the wattcoin view largely restates the enum's own description, so the baseline of 3 applies.

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?

The description names a specific verb and resource: "Full details for one bot or bundle by SKU," and enumerates exactly what those details include (inputs, outputs, runtime pin, license terms). It distinguishes itself from the sibling list_products, which only supplies SKUs, so an agent can pick the right tool 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?

It states an explicit prerequisite sequence — "Use after list_products, which provides SKUs" — and a conditional routing rule, "use site=wattcoin for the SOL-only wattcoin.org view." Alternative and condition are both named rather than inferred.

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