Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Delete Storage

delete_storage
DestructiveIdempotent

Delete a storage volume and its data, preview affected pods before confirming, and block deletion when a user pod still mounts it.

Instructions

Delete a storage volume and all data on it. storage is its pv_name or display name from the storages tool. With confirm=false (default) it only returns what would be deleted (including pods that still mount it); call again with confirm=true after the user agreed. Volumes mounted by a user pod are refused (storage_in_use). 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": {
      "storage": "<storage>"
    },
    "name": "delete_storage"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
storageYes
workspaceNo
operation_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the destructiveHint/idempotentHint annotations, it discloses what actually gets destroyed (the volume and its data, and it previews which pods would be affected), the refusal error path, and the full operation_id contract – reuse for retries, a new ID means a new operation. That is materially more than the annotations convey.

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?

Front-loaded with the destructive action, then the confirm flow, then the operation_id protocol – a sensible ordering. It is slightly over-long, with the confirmation instruction effectively restated in the operation_id paragraph ('Keep it for confirmation').

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?

An output schema exists, so return shape needn't be explained, and the destructive, retry, and refusal behaviors are all covered. The only real gap is the unexplained workspace parameter, which matters for scoping a delete in a multi-workspace account.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate, and it does for three of four parameters: storage (name source), confirm (default false, preview semantics), and operation_id (UUID, reuse on retry). The workspace parameter is never mentioned, leaving one ambiguity for a multi-tenant-scoped delete.

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?

States a specific verb and resource ('Delete a storage volume') plus the blast radius ('all data on it'), and it names the authoritative source for the identifier ('pv_name or display name from the storages tool'). That is enough to separate it from update_storage, create_storage, and connect_storage without opening any schema.

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?

It prescribes the exact two-step workflow: preview with confirm=false, then re-call with confirm=true only 'after the user agreed'. It also states the refusal condition (storage_in_use when a user pod mounts it) and routes post-timeout recovery to operation_status, so the agent knows both when to call and when not to proceed.

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