Skip to main content
Glama
Sign In
dos-mcp

dos-mcp

by 64kramsystem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

dosbox_swap_floppy

Switch the floppy disk image mounted in DOSBox drive A or B to the next image, enabling quick access to alternate disk contents without reloading the emulator.

Instructions

Advance the mounted floppy image in A: (0) or B: (1).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dosbox_swap_floppy"
  }
}

Input Schema

NameRequiredDescriptionDefault
driveNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. 'Advance' implies a mutation but lacks details on side effects (e.g., unmounting previous image, data loss risk, reversibility). It does not contradict annotations (none exist), but fails to add richer context for a write operation.

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 with no filler. It front-loads the action and immediately clarifies the parameter values. Perfectly concise and structured.

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 simple tool with one parameter and an output schema, the description covers the essential purpose and parameter semantics. It could be more complete regarding side effects, but given the simplicity and presence of an output schema, it's adequate.

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

Parameters4/5

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

The schema has one parameter 'drive' with no description and 0% coverage. The description compensates by explicitly mapping drive values 0 and 1 to A: and B:, which adds meaning beyond the bare schema. This is sufficient for the single parameter, though it doesn't cover edge cases like invalid values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Advance the mounted floppy image') and specifies the resource (floppy image in A: or B:). It distinguishes from sibling tools by focusing on floppy swapping, though it doesn't explicitly name alternatives.

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 description implies usage (when you need to advance to the next floppy image) but provides no explicit when-to-use or when-not-to-use guidance, nor does it mention alternative tools. The context is clear from the name, but no exclusions are stated.

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