Skip to main content
Glama
Sign In
crashwebsite-mcp

crashwebsite-mcp

Official
by PluginCrashReports
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_plugin

Permanently remove a plugin and all associated crash reports, symbols, and comments. Requires owner/admin authorization and confirmation via plugin code to prevent accidental deletion.

Instructions

Permanently delete a plugin and ALL its crashes, symbols and comments. Owner/admin only; irreversible.

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": {
      "confirm": "<confirm>"
    },
    "name": "delete_plugin"
  }
}

Input Schema

NameRequiredDescriptionDefault
pluginNoWhich plugin to query: id, plugin code, or name. Omit if you have only one; otherwise required (see list_plugins).
confirmYesMust equal the plugin's exact plugin_code, as a safety check, to actually delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior5/5

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

No annotations present; description fully discloses irreversible deletion of plugin and all associated crashes, symbols, and comments, plus authorization requirement.

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 concise sentences, front-loaded with primary action and key constraints. No wasted words.

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?

Given simple tool with 2 parameters and no annotations/output schema, description covers purpose, effects, authorization, and confirmation requirement completely.

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 covers 100% of parameters; description does not add significant extra meaning beyond what schema provides (plugin identification and confirmation).

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?

Description explicitly states 'Permanently delete a plugin' with clear verb and resource. Differentiates from sibling tools like add_plugin and list_plugins.

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?

Mentions 'Owner/admin only; irreversible', giving clear context for when to use (with authority and certainty) and implying when not to. No explicit alternatives, but context suffices.

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

Deploy Server

Other Tools