Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Restart Pod

restart_pod
Idempotent

Restart a pod in place on the same machine and storage, then poll pod status until running to confirm recovery.

Instructions

Restart a pod in place (same machine, same storage). Asynchronous — poll pods for running. A 401 from a port whose access is locked (pods tool) is the lock working; a restart doesn't change it. 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": "restart_pod"
  }
}

Input Schema

NameRequiredDescriptionDefault
podYes
workspaceNo
operation_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Annotations declare idempotentHint=true, destructiveHint=false, and readOnlyHint=false, and the description explains WHY: state is preserved (same machine, same storage) and idempotency is achieved by reusing the operation_id for confirmation and retries. It also discloses async behavior, the 401 lock semantics so a caller doesn't misread a lock as a failure, and the correct recovery path after a timeout.

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 key property before moving to the async and operation_id rules; almost every sentence carries operational weight. The 401/lock sentence is dense and interrupts the flow between the async note and the operation_id rules, which slightly hurts scannability.

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 a rich annotation set and an output schema present, the description covers the things structured data cannot: idempotency semantics, async completion detection, lock behavior, and timeout recovery. The main omission is any indication of what `workspace` scopes or what the caller should expect regarding the pod's prior state beyond storage and machine preservation.

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 carries the burden — and it does for operation_id, spelling out generate-vs-reuse, persistence across retries, and the consequence that a new ID creates a new operation. The `workspace` parameter is never mentioned and `pod` is left entirely implicit, so a third of the parameter surface remains undocumented.

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?

States a specific verb and resource ("Restart a pod") and adds scope detail — "in place (same machine, same storage)" — that separates it from a stop/start cycle implied by the sibling names start_pod, stop_pod, and create_pod. An agent can tell what operation it performs without opening the schema, though it never explicitly compares itself to those siblings.

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 invocation context: the call is asynchronous, the caller must poll pods for `running`, every write requires operation_id, and retries after a timeout should go through operation_status first. It lacks explicit when-not-to-use guidance (e.g., when to prefer stop_pod + start_pod instead of an in-place restart), but the operational flow is clear enough to act on.

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