Sigistry Plugin & Skill Catalog

Get a Claude Code plugin

get_plugin

Read-onlyIdempotent

Get the full details of a single Sigistry plugin by its id, including install commands, component counts, and its security-audit result (per-check pass/fail from the Verified by Sigistry methodology).

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

Input Schema

Name	Required	Description	Default
`id`	Yes	the plugin id, e.g. "sql-safety-net"

Output Schema

Name	Required	Description
`id`	Yes
`name`	Yes
`tags`	Yes	keywords from the marketplace entry
`agents`	Yes	relative paths to agent files
`author`	No
`counts`	Yes	component counts
`skills`	Yes	relative paths to skill manifests
`license`	No
`version`	No
`category`	No
`commands`	Yes	relative paths to command files
`homepage`	No
`description`	No
`verification`	No	security-audit result for this plugin (null when never audited)
`installCommand`	Yes	command to install this plugin
`searchableText`	Yes	lowercased text used for matching
`installMarketplace`	Yes	command to add the marketplace to Claude Code

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 1, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context about what details are returned (install commands, component counts, security-audit result) but does not disclose additional behavioral traits such as error cases or lookup semantics. No contradiction exists.

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?

The description is a single well-structured sentence that front-loads the core purpose ('Get the full details of a single Sigistry plugin by its id') and then adds valuable specifics. Every clause earns its place without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has one required parameter, a rich output schema, and annotations covering safety and idempotency, the description is complete enough for an agent to select and invoke it correctly. No critical contextual gap is apparent.

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%: the single required 'id' parameter is described with an example ('sql-safety-net'). The description only restates that lookup is by id, so it adds little meaning beyond the schema, which is acceptable at the baseline.

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?

The description uses a specific verb and resource: 'Get the full details of a single Sigistry plugin by its id.' It also lists concrete contents (install commands, component counts, security-audit result), which distinguishes it from sibling tools like get_skill and search_plugins.

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 clearly establishes the context: use this tool when you already have a plugin id and need full details for that single plugin. It does not explicitly name alternatives or exclusion cases, but the id-based single-item purpose is evident enough to guide selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Sigistry Plugin & Skill Catalog tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?