Skip to main content
Glama

PickAPlugin

Search plugins

search_plugins
Read-onlyIdempotent

Search the PickAPlugin catalog of ChatGPT, Codex and Claude plugins, agent skills and MCP servers by keyword (e.g. 'memory', 'postgres', 'code review', 'pdf'). Paid featured listings come first and are marked featured=true; everything else is ranked by relevance, then GitHub stars.

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_plugins"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 10, max 25).
queryYesKeywords describing what the plugin should do.
categoryNoOptional category name or slug from list_categories.

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 cover the safety profile (read-only, idempotent, non-destructive), so the bar is lower, and the description adds genuinely new behavior: paid featured listings are placed first and flagged featured=true, with remaining results ranked by relevance then GitHub stars. That ordering bias is critical for an agent interpreting results and is not derivable from the schema.

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 dense sentences with zero filler; scope is stated first, ranking behavior second. Query examples are embedded inline rather than bloating the text.

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?

There is no output schema, so the description carries the return-value burden, and it does explain result ordering and the featured flag. It still omits anything about result shape beyond featured, total counts, or truncation at the limit of 25.

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 adds real value by giving concrete keyword examples that guide query formulation and by tying category to list_categories. The limit and category constraints are left to the schema, which is appropriate.

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 states a specific verb and resource: search the PickAPlugin catalog of ChatGPT, Codex and Claude plugins, agent skills and MCP servers by keyword. It is immediately clear what the tool returns. It stops short of differentiating itself from top_plugins, leaving the agent to infer that keyword search differs from a top-listing browse.

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 implied rather than stated: the keyword examples ('memory', 'postgres', 'code review', 'pdf') show the intended input shape, and the category parameter is linked to list_categories, giving a navigational hint. There is no explicit when-to-use or when-to-prefer-top_plugins guidance.

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.