Skip to main content
Glama

PickAPlugin

Top plugins

top_plugins
Read-onlyIdempotent

Top plugins overall or in one category: paid featured listings first (marked featured=true), then editor's picks, then the most-starred maintained projects.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "top_plugins"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 10, max 25).
categoryNoOptional category name or slug from list_categories.

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?

Annotations already establish this as a safe, idempotent, closed-world read, so the description is not burdened with the safety profile. What it does add is genuinely non-obvious: the ranking algorithm, including that paid featured listings are surfaced first (marked featured=true), followed by editor's picks and then most-starred maintained projects — a monetization disclosure an agent could not infer from any structured field.

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?

A single sentence that front-loads the scope ('overall or in one category') and then spends its remainder on the one thing an agent cannot get elsewhere, the ordering rules. No filler and no repetition of schema or annotation content.

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, zero-required listing tool with no output schema, the definition covers scope, category mode, and result ordering. The main residual gap is that it never says what a result looks like (name, stars, URLs), though the ordering clause implies stars and a featured flag are present.

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 both parameters are fully documented in the schema itself (limit with default/min/max, category as name or slug from list_categories). The description's 'in one category' merely restates the category parameter and adds no format or constraint detail beyond it, making the baseline 3 correct.

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 resource and scope: 'Top plugins overall or in one category,' which tells an agent this is a ranked listing rather than a keyword search. It does not name search_plugins or explain how it differs from it, so sibling differentiation is left implicit.

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 phrase 'overall or in one category' implies two usage modes (browse everything vs. narrow by category), but there is no explicit when-to-use guidance, no exclusion against search_plugins, and no stated prerequisite for the category value beyond what the schema already says.

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.