Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

List Storage

storages
Read-onlyIdempotent

List storage volumes in a workspace or retrieve one by PV or display name, including capacity, available space, usage rate, and mounted pods.

Instructions

List the storage volumes in a workspace, or show one volume by its pv_name or display name. total_size and available_size are in MiB (divide by 1024 for GiB) and usage_rate is 0..1; linked_pods tells which pods mount the volume. workspace takes the id from the workspaces tool (a label also works); pass "all" for every workspace, or omit it if the user has only one.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "storages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo
storageNo
workspaceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely new context beyond that: units (MiB, usage_rate 0..1) and the meaning of `linked_pods`. It is silent on pagination behavior for a list tool with openWorldHint, which is a 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?

Three short sentences, each front-loaded with its topic: purpose first, then result-field semantics, then the workspace parameter rule. No restated title, no filler, and the MiB-to-GiB conversion note is a compact practical aid.

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?

With an output schema present and annotations covering safety, the description focuses on what structured fields don't say: lookup modes, units, and workspace scoping. The one notable omission is pagination — nothing tells the agent how `limit`/`cursor` behave or whether results are truncated.

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 0%, so the description bears the full burden. It handles `storage` (pv_name or display name) and `workspace` (id, label, "all", or omit) well, but says nothing about `limit` or `cursor`, leaving two of four parameters with no documented meaning anywhere.

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?

The first sentence names a specific verb and resource ('List the storage volumes in a workspace') and adds a second mode ('show one volume by its `pv_name` or display name'), so the agent knows the tool is a read/list operation with a single-item lookup. It implicitly contrasts with the create/delete/update/connect siblings through the verb, but never names an alternative tool explicitly.

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?

Clear guidance on mode selection (list vs single lookup) and a concrete rule for the workspace parameter: use the id from the workspaces tool, pass "all" for every workspace, or omit it when the user has only one. It stops short of stating when to reach for `pods` or `connect_storage` instead, so no explicit exclusions are present.

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