search_harnessesSearch the SuperSkill registry by task, job, title, summary or tag.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | No | Search terms such as market research, support triage or finance safety. |
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | ||
| code | Yes | ||
| status | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Output 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"
+}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.
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.
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.
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.
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.
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.
Add one secure layer between your agents and this server.
Most tools have distinct purposes, but there is some overlap among search variants (search, search_resources, search_harnesses) and between fetch and resource_detail, which could cause confusion.
Naming mostly follows a verb_noun pattern, but there are inconsistencies such as 'publish_markdown_to_harness' being longer and 'resource_use_instructions' having a different structure.
12 tools is appropriate for a registry server, covering search, fetch, publish, and pull operations without being overwhelming.
The tool set covers core operations (search, fetch, publish, pull) but lacks update and delete functionalities, which are minor gaps for a registry.