Skip to main content
Glama

Claude Plugins Directory

Get plugin details

get_plugin
Read-onlyIdempotent

Details for one plugin by its slug (from search_plugins): description, source, licence, stars, its skills, and install commands for Claude Code (and the Claude app for Anthropic's plugins).

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
slugYesPlugin slug, e.g. 'sales' or 'thedotmack-claude-mem'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds value beyond them by disclosing the payload contents — notably that it includes install commands scoped to Claude Code and the Claude app for Anthropic plugins — which tells the agent what it can do with the result.

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 identifying verb and resource, then the returned fields. Every clause carries information; nothing is redundant with the title or schema.

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 must carry the return-value burden, and it does so by enumerating the fields returned. Minor gaps remain — behavior on an unknown slug and the exact shape of 'its skills' (IDs vs. objects) are unstated — but nothing blocks 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% and the single parameter is already described with examples in the schema. The description still adds meaning the schema does not: that the slug originates from search_plugins, making the parameter's provenance and format contract explicit rather than just an example string.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Details for one plugin by its slug') and enumerates exactly what comes back: description, source, licence, stars, skills, and install commands. It also names the sibling that produces the input (search_plugins), so an agent can distinguish it from search_plugins/search_skills without opening a schema.

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?

The parenthetical '(from search_plugins)' tells the agent where the slug comes from, which establishes the intended workflow: search first, then fetch details. There is no explicit exclusion clause, but for a single-object getter with a clearly implied position after search, the guidance is unambiguous.

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