Skip to main content
Glama
Sign In
omv-mcp

omv-mcp

by vnaveenb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

stop_stack

Destructive

Take down all containers of a running stack on your NAS. Requires explicit confirmation to stop the stack.

Instructions

Stop a running stack (takes all its containers down). 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": "stop_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
stack_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description explains exactly what happens (takes all containers down) and adds a critical safety requirement (confirm=True). This informs the agent about the tool's behavior and preconditions beyond what annotations already convey.

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 two sentences long, front-loaded with the action, and every word serves a purpose. The parenthetical clarifies the effect without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple destructive operation with two parameters, the description adequately covers the purpose, the effect, and the mandatory confirmation flag. The absence of an output schema is not an issue since the tool likely returns a simple confirmation or status. The description is complete for an agent to use it correctly.

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?

The description adds meaning to the confirm parameter by explicitly requiring it to be true, but it does not explain stack_id, which is left to inference from its name. With 0% schema description coverage, the description partially compensates but could provide more detail on the stack_id parameter.

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 uses the specific verb 'Stop' with the resource 'running stack' and clarifies the effect ('takes all its containers down'). This clearly distinguishes it from siblings like start_stack and restart_stack.

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 provides clear context for when to use the tool (to stop a running stack), and the instruction 'Requires confirm=True' gives an explicit prerequisite. It doesn't mention alternatives or when not to use it, so it misses a perfect score.

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

Deploy Server

Other Tools