Skip to main content
Glama

Claude Plugins Directory

Search skills

search_skills
Read-onlyIdempotent

Find individual skills inside Claude plugins by what they do, e.g. 'contract review' or 'call prep'. Returns each skill's plugin and the command to run it.

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
limitNoDefault 10, max 25.
queryYesWords to match in the skill's name, description or plugin.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds value by disclosing the return payload — each skill's plugin and the command to run it — which is important since there is no output schema. It does not mention ranking or match behavior, which keeps it below 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?

Two sentences, zero waste: the core purpose and an illustrative example come first, followed by the return shape. Nothing is repeated from the schema or annotations.

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 two-parameter read-only search with no output schema, the description covers what it finds, how to phrase the query, and what comes back. Minor gaps remain around result ordering and whether matching is fuzzy or exact, but nothing prevents a correct call.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description's examples clarify that the query is a natural-language description of what the skill does rather than a literal skill name — meaning the schema's 'words to match in name, description or plugin' does not fully convey. The limit parameter is left entirely to the schema, which is acceptable.

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?

"Find individual skills inside Claude plugins by what they do" names a specific verb and resource and scopes it to skills rather than plugins, which implicitly separates it from search_plugins. It stops short of naming the sibling outright, so the differentiation relies on the agent noticing the 'individual skills' qualifier.

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 example queries ('contract review', 'call prep') imply the intended use case is task-based lookup, but there is no explicit statement of when to choose this over search_plugins or get_plugin, and no exclusions. Usage is inferable rather than stated.

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.

Resources