Skip to main content
Glama
superpowers-mcp

superpowers-mcp

by erophames

list_skills

Lists available superpowers skills with their descriptions and supporting files so LLMs can discover which skills the MCP server provides.

Instructions

List all available superpowers skills with their descriptions and supporting files

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It does disclose the shape of the result (descriptions and supporting files), which tells the agent this is a non-destructive read, but it says nothing about result size, ordering, or whether supporting files are listed as paths or contents.

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?

A single front-loaded sentence with no filler, hedging, or redundant restatement of the tool name. Every phrase (all, descriptions, supporting files) contributes information.

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 zero-parameter read tool with no output schema, the description covers what the tool returns and its scope of enumeration. It falls short only on practical invocation details such as whether the result can be large or whether supporting files require a follow-up call to get_skill_file.

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?

The tool takes zero parameters, so the schema has nothing to explain and the description has no parameter semantics to compensate for. The baseline of 4 applies; no parameter confusion is possible here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ("List") plus a clear resource ("superpowers skills") and states the returned payload: descriptions and supporting files. The word "all" implicitly contrasts with the filtered/recommendation siblings, but no sibling is named, so differentiation is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"List all available" implies the use case of full enumeration versus a targeted lookup, but the description never states when to prefer this over recommend_skills or semantic_search_skills, nor any exclusions. Usage is inferable rather than instructed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.