Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Delete Pod

delete_pod
DestructiveIdempotent

Permanently delete a pod with a preview-first flow: call without confirm to see what would be removed, then confirm to execute. Network storage survives; local volumes are deleted only if listed.

Instructions

Delete a pod permanently. With confirm=false (default) it only returns what would be deleted; call again with confirm=true after the user agreed. Attached network storage survives; local (hostPath) volumes are deleted only if listed in delete_local_storages by pv_name or display name on the preview. Confirm with the returned pod_name and storage ids: a display name is refused with confirm=true. Every write requires operation_id. Reuse the ID returned by the preview, or generate a UUID before the first call. Keep it for confirmation and all retries; a new ID means a new operation. After a timeout, check operation_status and resource state before retrying.

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": {
      "pod": "<pod>"
    },
    "name": "delete_pod"
  }
}

Input Schema

NameRequiredDescriptionDefault
podYes
confirmNo
workspaceNo
operation_idNo
delete_local_storagesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds real behaviour beyond them: what happens to attached network storage versus hostPath local volumes, the pv_name/display-name rule for delete_local_storages, and the operation_id retry contract. It does not explain that workspace is left untouched or what the preview payload contains, so a small gap remains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The destructive scope is front-loaded and each sentence carries operational content, including the general 'every write requires operation_id' rule that is genuinely relevant here. It is dense with long compound sentences and a slight run-on at the start, but no sentence is filler.

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?

For a destructive five-parameter tool with no schema descriptions, the definition covers preconditions, irreversible effects, the format constraint on confirmation identifiers, and retry behaviour. Return values need not be described because an output schema exists.

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?

Schema coverage is 0%, so the description has to carry all parameter meaning and largely does: confirm is the preview/execute switch with a stated default, delete_local_storages is keyed by pv_name or display name with the explicit constraint that a display name is refused when confirm=true, and operation_id gets full lifecycle semantics (reuse from preview or generate a UUID, keep across retries, new ID means new operation). Only workspace is left unexplained.

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?

Opens with a specific verb and resource ("Delete a pod permanently") and immediately qualifies the scope with the two-phase preview/confirm model, so an agent knows exactly what this tool does and that it is not a one-shot delete. The distinction from siblings like stop_pod or restart_pod is implicit in 'permanently' but the resource is unambiguous.

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

Usage Guidelines5/5

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

Explicit when-to-call sequencing: call first with confirm=false to get a preview, then call again with confirm=true only after the user agrees. It also names operation_status as the check after a timeout, giving a concrete alternative path rather than leaving recovery to inference.

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