Skip to main content
Glama
Sign In

SuperSkill Registry

by com.onlyharness
OverviewDiscussionsAdmin

Search harnesses

search_harnesses
Read-onlyIdempotent

Search the SuperSkill registry by task, job, title, summary or tag.

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": "search_harnesses"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoSearch terms such as market research, support triage or finance safety.

Output Schema

NameRequiredDescriptionDefault
okYes
codeYes
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, providing strong behavioral signals. The description adds that it searches by specific fields, but does not reveal additional behavioral traits beyond what annotations imply.

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, front-loaded sentence with no fluff. It could potentially include more detail about result format or pagination, but is efficient for its purpose.

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 the tool's simplicity (2 parameters, rich annotations, and presence of an output schema), the description provides sufficient information for basic usage. It may be slightly lean on explaining the scope of search (e.g., whether it searches all fields simultaneously), but overall complete.

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 50% (query has a description, limit does not). The tool description adds context that the query can be by task, job, title, summary, or tag, but this is already implied by the schema's example. No information is added about the 'limit' parameter.

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 the action (search), the resource (SuperSkill registry), and the fields to search by (task, job, title, summary, tag). It distinguishes itself from sibling tools like 'search' or 'search_docs' by specifying the registry context.

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?

No guidance is provided on when to use this tool versus its siblings (e.g., 'search', 'search_docs', 'search_resources'). There is no mention of prerequisites, exclusions, or context-dependent usage.

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

All SuperSkill Registry toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources