Skip to main content
Glama
Sign In
windows98-mcp

windows98-mcp

by ido-pluto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

vm_unlock

Idempotent

Release the current VM session lease to unlock the machine. Use force to override refusal when terminals or file transfers remain open.

Instructions

Release this session's VM lease. Normal unlock refuses while terminals or transfers remain open.

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_name": "<vm_name>"
    },
    "name": "vm_unlock"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNo
vm_nameYesUnique VM name configured in WIN98CTL.INI.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.7.0
    • addedInput schema / properties / vm_name
      Added value: +{
+  "description": "Unique VM name configured in WIN98CTL.INI.",
+  "pattern": "^[A-Za-z0-9][A-Za-z0-9._-]{0,63}$",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "vm_name"
+]
  2. First observedv0.0.0-development

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations, the description reveals an important nuance: a normal unlock refuses when terminals or transfers are open, implying that force changes this behavior. This adds meaningful context about failure modes and the existence of a non-normal mode, even though it does not fully spell out the exact effect of force.

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 short sentences with no filler: the first states the core purpose, the second adds a critical behavioral caveat. It is front-loaded and every word earns its place.

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?

For a low-complexity tool with helpful annotations and input schema, the description covers the main purpose and a key edge case. It could be more explicit about how force overrides the refusal and what the return behavior is, but those are not significant blockers given the schema and annotations.

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 schema documents vm_name but leaves force undescribed, giving only 50% coverage. The phrase 'Normal unlock refuses...' indirectly hints that force is the abnormal override mode, but it never explicitly connects force to that behavior. The description adds some meaning but still relies on inference.

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 opens with a concrete action—'Release this session's VM lease'—naming both the verb and resource precisely. It further distinguishes itself with the conditional behavior 'Normal unlock refuses while terminals or transfers remain open,' clearly separating it from sibling tools like vm_lock and other VM management actions.

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 gives clear context about when the unlock will fail (while terminals or transfers are open), which is directly useful for choosing the right invocation. It implies that the optional force parameter provides an alternative path, though it does not explicitly name sibling tools or state 'use force=true when you want to override.'

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