Skip to main content
Glama

get_plugin

Read-only

Get a plugin's metadata and schema (fields/defaults). Use before filling pluginData in a custom-plugin block.

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

Input Schema

NameRequiredDescriptionDefault
plugin_idYesPlugin id from list_plugins or propose_plugin_preview.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds the workflow sequencing (fetch before composing pluginData) but says nothing about error behavior for invalid ids or the size/shape of the returned metadata. With annotations doing the heavy lifting, this is adequate rather than rich.

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 sentences, zero filler, with the capability stated first and the usage constraint second. Every clause carries information an agent needs.

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, and the description partially compensates by indicating the return contains metadata and schema fields/defaults. For a single-parameter read tool with full annotation coverage, that is close to complete; only failure modes for a bad id are unstated.

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 plugin_id field already documents its source (list_plugins or propose_plugin_preview). The description adds no format, validation, or naming detail beyond the schema, so the baseline 3 applies.

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 ("Get a plugin's metadata and schema") and parenthetically clarifies the payload shape (fields/defaults), which separates it from list_plugins-style enumeration. It stops short of naming a sibling it is not, but the resource scope is unambiguous.

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 gives explicit ordering guidance — "Use before filling pluginData in a custom-plugin block" — which tells the agent exactly where this call sits in the workflow. It does not mention alternatives or what to do if the plugin id is unknown, so no exclusions are stated.

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