Skip to main content
Glama

enable_plugin

Activate a disabled Docker plugin to route API calls through it. Use timeout to control wait for plugin health.

Instructions

Activate an installed plugin so Docker routes relevant API calls through it.

Activates a plugin that is currently disabled — either freshly installed or previously disabled via disable_plugin. If the plugin exposes configuration (check via get_plugin), call configure_plugin while it is still disabled before enabling it. timeout controls how long Docker waits for the plugin process to become healthy; 0 means wait indefinitely.

args: name - Plugin name or id to enable timeout - Seconds to wait for the plugin to become healthy (0 = no timeout) returns: bool - True after the plugin is enabled

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
timeoutNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Discloses activation and healthy state requirement, and timeout meaning. Annotations (readOnlyHint=false, destructiveHint=false) are consistent. Could mention failure scenarios.

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 concise paragraphs: purpose, usage workflow, parameter details. Every sentence adds value; no fluff.

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?

Covers input, output (returns bool), and usage flow. References sibling tools (get_plugin, configure_plugin). Has output schema declaration.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description adds complete parameter semantics: name as 'plugin name or id', timeout as seconds to wait with special 0 meaning infinite wait.

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?

Clearly states the tool activates an installed plugin for Docker API routing, distinguishing it from related plugins like disable_plugin or configure_plugin.

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?

Provides explicit guidance on checking configuration via get_plugin before enabling and ordering with configure_plugin. Mentions timeout behavior. Lacks when-not-to-use (e.g., if not installed).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GavinLucas/docker-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server