omv-mcp

by vnaveenb

Overview Schema Source Related Servers Discussions Admin

Python

Local

restart_stack

Destructive

Stop then start a stack to restart it, with confirmation required to prevent unexpected downtime.

Instructions

Stop then start a stack (downtime during the cycle). Requires confirm=True.

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": {
      "stack_id": "<stack_id>"
    },
    "name": "restart_stack"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No
`stack_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Aug 2, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Beyond the destructiveHint annotation, the description adds useful behavioral context: the stop-start cycle and the downtime involved. It also emphasizes the confirm requirement, which is not fully captured by the annotation alone.

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?

The description is extremely concise: two short sentences that convey the core functionality, downtime warning, and confirmation requirement. Every word earns its place with no repetition or filler.

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?

Given the tool's simplicity (2 params, no output schema, destructive annotation), the description provides essential context: the operation, downtime, and confirm requirement. It does not mention error cases or what happens if confirm is false, but for this level of complexity it is reasonably complete.

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 compensates by explaining the critical parameter 'confirm' (must be true). The stack_id is left implicit but is straightforward given the tool name and schema type.

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?

The description clearly states the action: 'Stop then start a stack', which is a specific verb+resource combination. It distinguishes itself from siblings like start_stack and stop_stack by directly describing the composite restart operation.

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?

The description implies when to use this tool (to restart a stack) and explicitly states a key requirement: 'Requires confirm=True'. It also warns about downtime, setting clear expectations. However, it does not explicitly name alternatives or exclusions, so it falls short of a 5.

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