Skip to main content
Glama
Sign In

WattCoin

by io.github.WattCoin-Org
OverviewDiscussionsAdmin

WattCoin: Get skill

get_skill
Read-onlyIdempotent

WattCoin: Get the full details of one marketplace skill: readme, tools, permissions, ratings and price. Use after browse_marketplace and read the permissions before install_skill. No auth needed; read-only and live; returns a text summary.

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>"
    },
    "name": "get_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
skill_idYesSkill ID from browse_marketplace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

The description goes beyond annotations by adding 'No auth needed,' stating it is 'live,' and specifying the output is a 'text summary.'

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?

The description is extremely efficient, front-loading the function and then immediately providing critical constraints and workflow logic in a highly dense and valuable format.

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?

It provides all the necessary context for use, covering the data points returned, the required prerequisites (use after browsing), and the safety context (permissions before installing).

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%, so the schema provides all necessary technical details. The description merely repeats context already available or is slightly redundant, placing it at the baseline score.

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 clearly identifies the resource (marketplace skill) and lists specific data points it returns, such as 'readme, tools, permissions, ratings and price.'

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 provides explicit workflow guidelines: 'Use after browse_marketplace' and warns the agent to 'read the permissions before install_skill,' linking usage to other sibling tools.

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