Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Connect to Storage

connect_storage

Get an SSH login to a storage volume's files by returning a command and a one-time password that expires in minutes; use confirm to check readiness before issuing credentials.

Instructions

Get an SSH login to a storage volume's files, like the console's Connect, only when the user asks to connect: the command to run and a one-time password that expires in a few minutes (expires_at). storage is its pv_name or display name from the storages tool. Encrypted storage is unlocked and an access pod is started for it; it locks again by itself after auto_lock_minutes (remaining_seconds left). Other storage is reached through the access pod that already runs for it. With confirm=false (default) it only returns the storage's connection state and changes nothing; call again with confirm=true after the user agreed. It needs a read & write key. The confirmed call waits up to wait seconds (0-90, default 60) for the storage to be ready; if it isn't yet, the result has no password and says to call again. Give the command and password to the user and nobody else: never run the command yourself or put the password in files, commits or other tools. Each confirmed call issues a new password. The server keeps no operation record of this call, so operation_status can't look it up and a repeated confirmed call runs again.

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": "connect_storage"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNo
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?

Goes well beyond the annotations: discloses that encrypted storage gets unlocked and an access pod started with auto-lock timing, that a read & write key is required, that the password expires in minutes, that each confirmed call issues a new password, that the wait timeout is capped at 90s, and that no operation record exists so operation_status cannot track it. Everything is consistent with readOnlyHint=false and idempotentHint=false.

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?

Dense with useful content and roughly front-loaded, but a few sentences are convoluted, notably the encrypted-vs-plain access pod sentence. Most content earns its place; little is wasted.

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?

For a side-effecting, credential-issuing tool with an output schema available, the description covers the safety profile, the confirm flow, timing, and post-call behavior well. The remaining gap is the unexplained `workspace` and `operation_id` inputs, which an agent may still need to reason about.

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 coverage the description carries the load and does well for `storage` (pv_name or display name), `confirm` (default behavior and result), and `wait` (range 0-90, default 60, purpose). However, `workspace` and `operation_id` are never explained, leaving two of five parameters undocumented anywhere.

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: get an SSH login to a storage volume's files, contrasted with the console's Connect and with the `storages` tool used to resolve the name. An agent can immediately tell what the tool produces (a command and a one-time password).

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?

Explicitly gates usage: 'only when the user asks to connect', plus a clear two-step flow (confirm=false to inspect state, then confirm=true after the user agrees). It also routes name resolution to the `storages` tool and says what to do when the storage isn't ready yet (call again).

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