Skip to main content
Glama

PickAPlugin

Get plugin

get_plugin
Read-onlyIdempotent

Full details for one listing by its slug (from a search result or a pickaplugin.com/p/ URL): summary, category, maker, repo, homepage, docs, install command, stars, license.

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": {
      "slug": "<slug>"
    },
    "name": "get_plugin"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesListing slug, e.g. 'deja', or a pickaplugin.com/p/<slug> URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 behavior, so the safety profile is covered. The description adds value beyond them by disclosing the response shape — the exact set of fields returned — which is important because there is no output schema. It says nothing about failure behavior for an unknown slug, keeping it below the top mark.

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?

One sentence, front-loaded with the action and scope, with the provenance hint and field list packed into compact parentheticals. No sentence is wasted and nothing is repeated.

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 one-parameter read tool with rich annotations, the description covers purpose, slug provenance, and return fields — enough to invoke it correctly. The only gap is unstated behavior when a slug does not resolve, which is minor given the closed-world, read-only profile.

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% and the single slug parameter is already documented in the schema, including the URL-form example. The description's parenthetical repeats the same slug-or-URL semantics, adding no new syntax or format guidance. Baseline 3 applies when the schema carries the parameter burden.

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 opens with a specific verb and scope, "Full details for one listing by its slug," then enumerates the returned fields (summary, category, maker, repo, install command, stars, license). The singular "one listing" implicitly contrasts with the list-returning siblings, but no sibling is named, so differentiation is inferential rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It tells the agent where a valid slug comes from — a prior search result or a pickaplugin.com/p/<slug> URL — which is real usage context that establishes the follow-up workflow after search_plugins. It stops short of stating when not to use it (e.g., when you only have a name and should search first), so it is clear context without exclusions.

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.