dos-mcp

Overview Schema Source Related Servers Discussions Admin

dosbox_save_state

Capture a snapshot of the running DOSBox-X session and write it to an absolute host path, preserving exact state for later restoration or analysis.

Instructions

Save emulator state to an absolute host path.

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": {
      "path": "<path>"
    },
    "name": "dosbox_save_state"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes
`overwrite`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 21, 2026

TDQS

B3.2/5.0

Behavior2/5

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

Without annotations, the description should disclose side effects (e.g., overwriting files, performance impact). It only says 'save' which implies persistence, but does not mention the overwrite behavior (though the parameter exists) or any failure modes. Minimal transparency beyond the core action.

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 a single sentence that delivers the core message without verbosity. It is front-loaded and easy to scan, striking an appropriate balance for a simple tool.

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

Completeness2/5

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

For a simple save operation with two parameters stunt, the description is too sparse. It does not explain the overwrite flag, mention any prerequisites (like the emulator being running), or provide context on what happens on success/failure. Even though an output schema exists, the lack of behavioral details leaves the agent guessing on edge cases.

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?

Description clarifies that 'path' is an absolute host path (useful), but provides no explanation for 'overwrite' or its default false behavior. Given 0% schema coverage, the description partially compensates for path but leaves the other parameter unspecified, so a 3 seems fair.

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 specific action: save emulator state to an absolute host path. It distinguishes itself from sibling tools like 'dosbox_load_state' (loads) and 'dosbox_status' (queries), making the purpose unambiguous.

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 is provided on when to use this tool versus alternatives, or when it should be avoided. For example, it doesn't mention it's useful for preserving game state before closing, or that it should not be used while the emulator is running. The description is purely functional with no context.

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

Deploy Server