plugin_unload
Unload a loaded plugin by its name or instance ID.
Instructions
Unload a loaded plugin by plugin name or instance ID
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| pluginName | Yes |
Unload a loaded plugin by its name or instance ID.
Unload a loaded plugin by plugin name or instance ID
| Name | Required | Description | Default |
|---|---|---|---|
| pluginName | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. Description only implies a destructive action but does not disclose side effects, reversibility, or required permissions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, no redundant information. Could potentially include a brief note on parameter usage, but overall efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and no annotations, the description is insufficient. Does not explain what happens after unloading, confirmation, or error conditions.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Only one parameter (pluginName) with 0% schema description coverage. Description adds that it can be a name or instance ID, but this is ambiguous since schema expects a string without clarifying format.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the action (unload) and resource (plugin), with specific criteria (by name or instance ID). Distinguishes from sibling tools like plugin_load and plugin_list.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool vs alternatives. No mention of prerequisites or when not to unload a plugin.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/sole03/governflow'
If you have feedback or need assistance with the MCP directory API, please join our Discord server