Nemeton MCP

Overview Schema Source Related Servers Discussions Admin

stop_vm

Gracefully shut down a running virtual machine by providing its name or identifier. Ensures a clean stop to prevent data corruption.

Instructions

Gracefully shut down a running VM.

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": {
      "vm": "<vm>"
    },
    "name": "stop_vm"
  }
}

Input Schema

Name	Required	Description	Default
`vm`	Yes	VM name or identifier

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 8, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. 'Gracefully shut down' hints at behavior (clean shutdown) but lacks details like timeout, action if already stopped, or whether it waits for OS.

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?

Short and direct single sentence. Front-loaded with action and resource. Could be slightly improved by adding a sentence on usage, but current is efficient.

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

Completeness3/5

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

Tool is simple (one param, no output schema). Description covers basic purpose but does not explain post-shutdown state or edge cases. Adequate but not comprehensive.

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 coverage is 100% for the single parameter 'vm'. Description does not add meaning beyond 'VM name or identifier' already in schema.

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 ('gracefully shut down') and the resource ('running VM'). It distinguishes from 'force_stop_vm' by using 'gracefully', implying a clean shutdown.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this vs alternatives like 'force_stop_vm'. Does not mention that force_stop_vm is for emergencies.

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