Skip to main content
Glama
Sign In

WattCoin

by io.github.WattCoin-Org
OverviewDiscussionsAdmin

WattCoin: Rate skill

rate_skill
Idempotent

WattCoin: Rate a marketplace skill from 1 to 5 stars. Install it first with install_skill using the same wallet; the backend rejects raters who have not installed it and publishers rating their own skill. Resubmitting updates your earlier rating instead of adding a new one. No agent key needed. Returns the new average and rating count as text.

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": {
      "skill_id": "<skill_id>",
      "wallet": "<wallet>",
      "rating": "<rating>"
    },
    "name": "rate_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
ratingYesStar rating, integer 1-5
walletYesSolana wallet address, base58, 32-44 characters (e.g. 7vvNk...). The same wallet used for install_skill
skill_idYesSkill ID to rate, from browse_marketplace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / rating / description
      Previous value: -"1 to 5 stars"New value: +"Star rating, integer 1-5"
    • changedInput schema / properties / skill_id / description
      Previous value: -"Skill ID to rate"New value: +"Skill ID to rate, from browse_marketplace"
    • changedInput schema / properties / wallet / description
      Previous value: -"Your Solana wallet (must have installed the skill)"New value: +"Solana wallet address, base58, 32-44 characters (e.g. 7vvNk...). The same wallet used for install_skill"
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing backend validation rules (install requirement, self-rating block), the update-on-resubmit semantics, that no agent key is needed, and the return shape (new average and rating count as text). The idempotentHint is confirmed and enriched with concrete behavior.

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?

Four tight sentences, front-loaded with purpose, then prerequisites, then idempotency, then return value. No filler.

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?

Despite having no output schema, the description states what is returned (new average and rating count as text), and it covers auth, prerequisites, and mutation semantics. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all three parameters. The description adds a meaningful cross-tool constraint: the wallet must be the same one used for install_skill, which the schema only hints at.

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 ('Rate a marketplace skill') plus the value domain (1 to 5 stars), which cleanly separates it from siblings like install_skill or get_skill.

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 names the prerequisite tool (install_skill with the same wallet) and the two rejection conditions: raters who have not installed the skill and publishers rating their own skill. It also clarifies that resubmitting updates rather than duplicates, so an agent knows when to call it again.

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