Skip to main content
Glama

search_skills

Search the skills-hub.ai catalog for AI coding skills. Returns matching skills with metadata. 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, max 50)
queryYesSearch query (e.g. 'code review', 'testing React')
categoryNoFilter by category slug (e.g. 'review', 'test', 'build')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full behavioral burden, and it does disclose the return shape ('matching skills with metadata') and a mandatory presentation behavior (include each skill's `url`). The implicit read-only nature of 'search' is also clear. It does not mention auth requirements, rate limits, or result ordering, which keeps it short of a 5.

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 short sentences: purpose first, return shape second, output-navigation instruction third. Nothing is redundant and the most important routing information is front-loaded.

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?

With no output schema, the description usefully states what comes back and how to surface it (the `url` field). For a simple three-parameter read tool with fully documented parameters, this is close to complete; only empty-result or pagination behavior is unaddressed.

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 the schema already documents query, limit (default 10, max 50), and category slug with an example. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 gives a specific verb and resource: 'Search the skills-hub.ai catalog for AI coding skills.' That is unambiguous about what the tool does. It does not explicitly contrast itself with siblings such as list_installed_skills or get_skill_detail, so the catalog-vs-installed distinction must be inferred from the word 'catalog'.

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 is only implied: searching a catalog suggests discovery/browsing, which distinguishes it from listing installed skills. There is no explicit when-to-use statement, no exclusions, and no named alternative for the case where the user already knows the skill name (get_skill_detail).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.