Skip to main content
Glama
Sign In
windows98-mcp

windows98-mcp

by ido-pluto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

qemu_vm_restart

Destructive

Restart a managed QEMU VM by gracefully stopping it first, then powering it back on to apply changes or recover from issues.

Instructions

Gracefully stop then restart a managed QEMU 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_id": "<vm_id>"
    },
    "name": "qemu_vm_restart"
  }
}

Input Schema

NameRequiredDescriptionDefault
vm_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already mark the operation destructive, and the description adds the meaningful detail that the stop is graceful before restart. However, it does not disclose consequences such as downtime, loss of unsaved guest state, or behavior if the VM is not running.

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?

One concise, front-loaded sentence with no filler; every word contributes to scope and method.

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?

Adequate for a simple one-parameter restart tool, but with no output schema and no mention of prerequisites, return behavior, or failure conditions, an agent cannot fully anticipate edge cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description does not explain vm_id beyond referring to the managed VM. The parameter name and pattern offer some guidance, but the description fails to compensate for the missing schema descriptions.

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 ('restart') and resource ('managed QEMU VM'), and clarifies the method ('gracefully stop then restart'), distinguishing it from sibling tools like force_stop, shutdown, or start.

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

Usage Guidelines3/5

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

The graceful restart semantics imply when it should be used, but it does not explicitly contrast with alternatives such as qemu_vm_force_stop or state prerequisites like 'VM must be running'.

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