Skip to main content
Glama
superpowers-mcp

superpowers-mcp

by erophames

recommend_skills

Recommends relevant skills for a task using semantic ranking and workflow policy boosts, with optional project context and a configurable result limit.

Instructions

Recommend the most relevant skills for a task using semantic ranking and workflow policy boosts.

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": {
      "task": "<task>"
    },
    "name": "recommend_skills"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesTask description or user request.
max_resultsNoMaximum number of recommendations to return.
repo_contextNoOptional project context for better matching.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the ranking behavior ('semantic ranking and workflow policy boosts'), which is real behavioral information beyond the schema, but it says nothing about side effects, determinism, latency/cost, or that the operation is read-only.

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 well-formed sentence with no filler, leading with the action and resource before the mechanism. Nothing needs to be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the description should say more about what comes back (ranked list? scores? skill identifiers?) and whether the call has any side effects. The mechanism mention partially compensates, but an agent still lacks a complete picture for a recommendation tool with three parameters.

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%, so all three parameters (task, max_results, repo_context) are already documented in the schema. The description adds no extra meaning about how repo_context influences matching or how boosts interact with the ranking, so the baseline 3 is appropriate.

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 names a specific verb ('Recommend') and resource ('skills') and adds the mechanism ('semantic ranking and workflow policy boosts'), which distinguishes it from a plain listing tool like list_skills. It stops short of naming which sibling it should be chosen over, so an agent must still infer the boundary against semantic_search_skills.

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

Usage Guidelines2/5

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

There is no explicit when-to-use, when-not-to-use, or alternative named. The phrase 'for a task' hints at the input context, but nothing tells an agent why it should pick this over semantic_search_skills, list_skills, or compose_workflow.

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