Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Edit Storage

update_storage
Idempotent

Rename a storage volume, grow its capacity, or configure usage warnings with a preview-first workflow; confirm to apply changes, with growth billed hourly and irreversible shrinkage blocked.

Instructions

Change a storage volume like the console's Edit: rename it (name), grow it (size_gb, in GiB) or set its usage warning (usage_warning on/off, usage_warning_threshold 0-1). Pass only what changes; storage is the pv_name or display name from the storages tool. Storage can grow but never shrink (storage_cannot_shrink), and growing raises its hourly price, which is billed for as long as the volume exists. With confirm=false (default) it only returns the estimate (new and current size and hourly price) and changes nothing; call again with confirm=true after the user agreed. Growing runs asynchronously; renaming and the usage warning apply right away. 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": "update_storage"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
confirmNo
size_gbNo
storageYes
workspaceNo
operation_idNo
usage_warningNo
usage_warning_thresholdNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: grow-only (storage_cannot_shrink), the hourly-price/billing consequence of growing, that growth is asynchronous while rename and warning changes apply immediately, that confirm=false is a no-op preview, and the operation_id idempotency contract with timeout/retry guidance via operation_status. This is exactly the operational context annotations cannot express.

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 action and its editable fields, then the constraints, then the workflow, then the operation_id contract. Dense but every sentence carries information; the parenthetical restating the estimate contents is the only slightly redundant bit.

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 the brief mention of the estimate return is supplementary rather than required. For an 8-parameter mutation with async side effects and billing impact, the description covers nearly everything an agent needs; only the `workspace` parameter's role is unaddressed.

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?

With 0% schema description coverage, the description must carry the load and largely does: it defines `storage` as a pv_name or display name, `size_gb` in GiB, `usage_warning_threshold` as 0-1, `confirm` as preview-vs-apply, and `operation_id` as a reusable UUID. Only the `workspace` parameter 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?

States a specific verb and resource ("Change a storage volume") and enumerates exactly what can be changed: name, size_gb, usage_warning, usage_warning_threshold. An agent can distinguish this from create_storage, delete_storage, or connect_storage without opening the schema.

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?

Gives concrete procedural guidance: "Pass only what changes," the confirm=false preview-then-confirm=true workflow, and a pointer to the storages tool for the `storage` identifier. It does not explicitly rule out create/delete intent or name those siblings, but the context is clear enough to select the tool correctly.

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