Skip to main content
Glama
Sign In
dos-mcp

dos-mcp

by 64kramsystem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

dosbox_break_on_next_exec

Set a breakpoint at the next DOS EXEC entry point during debugging. Enable or disable this breakpoint to pause emulation when a program launches, helping analyze process startup in DOSBox-X.

Instructions

Break GDB at the next DOS EXEC entry point.

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_break_on_next_exec"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It does not disclose side effects (e.g., whether breakpoint is one-time or persistent), any required state (GDB attached), or what happens after the break. The word 'next' implies a one-shot action but leaves ambiguity.

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?

A single concise sentence that is front-loaded with the key action and target. No wasteful words; every word contributes to understanding the core purpose.

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 tool is simple with one parametrized boolean and an output schema, but the description omits the parameter's function and any details about the breakpoint behavior. It is minimally complete for a trivially simple action, but could clarify the 'enabled' semantics.

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 coverage is 0%, and the description does not explain the 'enabled' parameter (default true). The meaning (enable/disable the breakpoint) is absent, leaving the agent to guess. The description adds no value beyond the schema.

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 action ('Break GDB') and the target ('the next DOS EXEC entry point'). It distinguishes itself from sibling tools which handle screen capture, state management, input, and memory—none of which relate to breakpoints.

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 its use for debugging (breaking at a DOS EXEC) but provides no explicit context on when to use it versus alternatives, nor any conditions or prerequisites (e.g., GDB must be running). No exclusions or alternative tool mentions.

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