Skip to main content
Glama
Sign In
windows98-mcp

windows98-mcp

by ido-pluto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

directory_push

Destructive

Merge a host directory into a Windows 98 guest VM without deleting unrelated files. Use when you need to add or update files; the VM remains locked until vm_unlock is called.

Instructions

Merge-copy a host directory into the guest without deleting unrelated guest files. VM remains locked by this session; call vm_unlock when finished.

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": {
      "host_path": "<host_path>",
      "guest_path": "<guest_path>",
      "vm_name": "<vm_name>"
    },
    "name": "directory_push"
  }
}

Input Schema

NameRequiredDescriptionDefault
vm_nameYesUnique VM name configured in WIN98CTL.INI.
host_pathYes
overwriteNo
guest_pathYes

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"
+}
    • changedInput schema / required
      Previous value: -[
-  "host_path",
-  "guest_path"
-]New value: +[
+  "host_path",
+  "guest_path",
+  "vm_name"
+]
  2. First observedv0.0.0-development

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (destructiveHint=true, readOnlyHint=false), the description discloses an important non-obvious behavior: the VM remains locked after the call and requires vm_unlock. It also clarifies that unrelated guest files are preserved, which adds nuance to the destructive hint. No contradiction with annotations.

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?

Two sentences with no redundancy. The core merge-copy behavior and its key guarantee are front-loaded, and the lock/unlock instruction is the only additional context. Every sentence earns its place.

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?

The description is sufficient for the core operation and the critical lock workflow, but it leaves gaps around the overwrite parameter and any result or confirmation behavior. With no output schema and low parameter coverage, the missing overwrite semantics are a notable gap for a destructive-capable tool.

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 only 25%; only vm_name has a schema description. The description adds that host_path and guest_path are directories, but it does not explain the overwrite parameter, path format expectations, or how host_path/guest_path relate to one another beyond the copy direction.

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 names a specific verb and resource: 'Merge-copy a host directory into the guest.' It also explicitly scopes the behavior with 'without deleting unrelated guest files,' which differentiates it from a replace-style directory push and from siblings like file_push or directory_pull.

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 usage context: the VM is already locked by this session, and the caller must call vm_unlock when finished. It does not explicitly name alternatives, so there are no exclusion rules, but the context is strong enough for an agent to know the intended workflow.

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