SuperSkill Registry

Search agent resources

search_resources

Read-onlyIdempotent

Search mixed source-aware resources: harnesses, skills, plugins, workflows, MCP servers, configs, guides, runtimes and directories.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Alias for query, matching the HTTP /resources?q= contract.
`type`	No	Optional resource type filter, for example skill, plugin, workflow, mcp_server or harness.
`limit`	No
`query`	No	Search terms such as superpowers, MCP browser, workflow or Claude skill.
`worksWith`	No	Optional compatibility filter: claude-code, codex, cursor, mcp, cli or github.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes
`code`	Yes
`status`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "code": {
+      "const": "OK",
+      "type": "string"
+    },
+    "ok": {
+      "const": true,
+      "type": "boolean"
+    },
+    "status": {
+      "maximum": 599,
+      "minimum": 100,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "ok",
+    "code",
+    "status"
+  ],
+  "type": "object"
+}

AddedJul 7, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare `readOnlyHint: true` and `idempotentHint: true`, so the description does not need to repeat safety. It adds that the tool searches across various resource types, which provides some behavioral context beyond annotations but is minimal.

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 description is a single sentence that efficiently communicates the tool's scope. However, the phrase 'mixed source-aware resources' could be clarified for broader understanding.

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?

Given that an output schema exists and schema coverage is high, the description does not need to elaborate on return values. It sufficiently covers the tool's search scope across multiple resource types, making it complete for its simplicity.

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

Parameters2/5

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

Schema description coverage is stated at 80% (though all parameters appear described). The description adds little beyond the schema: it lists resource types but does not clarify parameter usage, defaults, or specific semantics. For example, `q` and `query` are both present but the description does not explain their relationship or when to use each.

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 states that the tool searches across multiple specific resource types like harnesses, skills, plugins, etc., using the verb 'Search' and enumerating the resource categories, which distinguishes it from sibling tools like `search` and `search_harnesses`.

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?

The description implies usage for broad resource searches but does not explicitly state when to use this tool versus alternatives like `resource_detail`, `search_harnesses`, or `search`. No exclusions or prerequisites are mentioned.

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

All SuperSkill Registry tools Inspect

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.