Skip to main content
Glama

list_plugins

Read-only

List installed plugins (core + user custom). Use returned plugin IDs to inspect or manage plugins. Call get_plugin for schema/defaults of a specific plugin.

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": "list_plugins"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds value beyond that by disclosing what the result contains (plugin IDs usable as input to other tools) and how to chain into get_plugin. It does not describe pagination or whether disabled plugins are included, which keeps it from a 5.

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?

Three short sentences with no filler: purpose and scope first, then how to use the output, then the sibling routing hint. Every sentence carries a distinct, actionable fact.

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 zero-parameter, read-only listing tool with no output schema, the definition covers purpose, scope, output content hint, and next step. Remaining gaps (result ordering, pagination, inclusion of disabled plugins) are minor for a tool this simple, and the annotations carry the safety dimension.

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?

The tool takes zero parameters, so there is no parameter meaning to compensate for; the baseline for an empty schema applies. No evidence of misleading or undocumented input expectations.

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?

Names a specific verb and resource ("List installed plugins") and immediately bounds the scope with "(core + user custom)". It also differentiates itself from the sibling get_plugin by stating that get_plugin handles schema/defaults for a single plugin, so an agent can distinguish the two 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?

Gives concrete downstream guidance: use the returned plugin IDs to inspect or manage plugins, and route to get_plugin when schema/defaults for one plugin are needed. It stops short of stating exclusions such as when not to enumerate (e.g., a single plugin is already known), but the routing condition is explicit enough to select correctly.

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