Skip to main content
Glama
@skills-hub-ai/mcp

@skills-hub-ai/mcp

search_skills

Search the skills-hub.ai catalog by query to find relevant skills, optionally include organization-private results, and return each skill's URL for display.

Instructions

Search the skills-hub.ai catalog for skills matching a query. Supports org-scoped search to include organization-private skills (requires SKILLS_HUB_API_TOKEN). Each result includes a url to the skill's page on skills-hub.ai; show that link to the user alongside each skill you mention.

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": {
      "query": "<query>"
    },
    "name": "search_skills"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 10)
queryYesSearch query (e.g. 'code review', 'testing React')
categoryNoFilter by category slug (e.g. 'review', 'test', 'build')
organizationNoOrganization slug to include org-private skills in results (requires authentication)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.13

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does add real value: the auth token requirement for org-scoped results and the presence of a `url` field in each result. It omits failure behavior when the token is missing, result ordering/ranking, and whether `limit` has a ceiling.

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?

Three sentences, front-loaded with purpose, then the org-scoping caveat, then the output-handling instruction. No filler and nothing buried.

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 four-parameter search tool with no output schema or annotations, the description covers purpose, auth prerequisites for private results, and the shape of returned items (via `url`). Pagination and empty-result behavior remain unaddressed but are minor for this tool class.

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 coverage is 100%, so all four parameters are already documented, establishing a baseline of 3. The description contributes only the concrete token name for the `organization` parameter's authentication requirement, a marginal addition over what the schema already says.

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?

States a specific verb and resource: 'Search the skills-hub.ai catalog for skills matching a query.' That clearly separates it from list_installed_skills and install_skill, though it never names or contrasts with those siblings explicitly.

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?

Usage context is implied (search the remote catalog rather than installed skills) and the org-scoped mode has a clear prerequisite: requires SKILLS_HUB_API_TOKEN. But there is no explicit guidance on when to use get_skill_detail instead, or what to do when search returns nothing.

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