Skip to main content
Glama

delete_plugin

Destructive

Delete a custom plugin created via propose_plugin_preview. Core plugins (counter-block, stat-block, cta-block) cannot be deleted.

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

Input Schema

NameRequiredDescriptionDefault
plugin_idYesThe plugin id returned by propose_plugin_preview.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description need not re-assert that this is a mutation. It does add real behavioral value the annotations cannot: the set of plugins immune to deletion and the requirement that the target must have originated from propose_plugin_preview. A note on irreversibility of the deletion would close the remaining gap.

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 short sentences, no filler, and the operation is front-loaded before the constraint. Every clause earns its place by either defining scope or preventing a bad call.

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 one-parameter destructive tool with full annotation coverage and no output schema, the definition supplies what matters: what it acts on, what it refuses to act on, and how to obtain the id. Only the post-deletion/error semantics are left unstated, which is a minor omission at this complexity.

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 single parameter is already documented as 'the plugin id returned by propose_plugin_preview'; the description only echoes that provenance link. It adds no format, example, or acceptance 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?

States a specific verb and resource ('Delete a custom plugin') and adds provenance ('created via propose_plugin_preview'), which implicitly scopes it away from the read/list siblings. The protected-plugin clause further sharpens what object class this tool operates on, though no sibling tool is named as an alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides an explicit exclusion ('Core plugins ... cannot be deleted'), which is genuine when-not guidance. However, it gives no positive routing guidance — nothing tells the agent which tool to use for inspecting plugins first (get_plugin, list_plugins) or what to do when deletion is refused.

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