Skip to main content
Glama
basementstudio

MCP DOS - Classic DOS Gaming Server

List DOS Games

Read-onlyIdempotent

Browse and discover all available classic DOS games like DOOM, Super Mario, and Duke Nukem 3D that you can play through the MCP DOS gaming server.

Instructions

List all available DOS games

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the tool logic: lists keys from DOS_GAMES and returns formatted content.
    export default async function list() {
      const games = Object.keys(DOS_GAMES);
      return {
        content: [
          { type: "text", text: JSON.stringify(games, null, 2) },
          { type: "text", text: "To play a game, use the `open-dos` tool and pass the game key as argument." }
        ]
      };
    }
  • Empty schema indicating the tool takes no input parameters.
    export const schema = {}
  • src/tools/list.ts:5-14 (registration)
    Metadata registration defining the tool's name, description, and annotations.
    export const metadata = {
      name: "List DOS Games",
      description: "List all available DOS games",
      annotations: {
        title: "List DOS games availables",
        readOnlyHint: true,
        destructiveHint: false,
        idempotentHint: true,
      },
    }
  • Supporting data structure providing the list of DOS games used in the handler.
    export const DOS_GAMES: Record<string, {
      file: string;
      executable: string;
      title: string;
      cdnFile?: string;
      keys: KeyMapping[];
    }> = {
      'doom': {
        file: "upload/DOOM-@evilution.zip",
        executable: "./DOOM/DOOM.EXE",
        title: "DOOM",
        cdnFile: "https://js-dos.com/cdn/upload/DOOM-@evilution.zip",
        keys: [
          { code: -1, key: 'No action' },
          { code: 38, key: 'ArrowUp', text: 'Forward' },
          { code: 40, key: 'ArrowDown', text: 'Back' },
          { code: 37, key: 'ArrowLeft', text: 'Left' },
          { code: 39, key: 'ArrowRight', text: 'Right' },
          { code: 87, key: 'KeyW', text: 'Use' },
          { code: 83, key: 'KeyS', text: 'Fire' },
          { code: 65, key: 'KeyA', text: 'Strafe left' },
          { code: 68, key: 'KeyD', text: 'Strafe right' },
          { code: 13, key: 'Enter' },
        ]
      },
      'super-mario': {
        file: "upload/mario-colin.zip",
        executable: "./Mario.exe",
        title: "Super Mario",
        cdnFile: "https://js-dos.com/cdn/upload/mario-colin.zip",
        keys: [
          { code: -1, key: 'No action' },
          { code: 37, key: 'ArrowLeft', text: 'Left' },
          { code: 39, key: 'ArrowRight', text: 'Right' },
          { code: 18, key: 'AltLeft', text: 'Jump' },
        ]
      },
      'tetris': {
        file: "upload/Tetris-neozeed.zip",
        executable: "./",
        title: "Tetris",
        cdnFile: "https://js-dos.com/cdn/upload/Tetris-neozeed.zip",
        keys: [
          { code: -1, key: 'No action' },
          { code: 55, key: 'Digit7', text: 'Left' },
          { code: 56, key: 'Digit8', text: 'Right' },
          { code: 57, key: 'Digit9', text: 'Rotate' },
          { code: 32, key: 'Space', text: 'Drop' },
          { code: 13, key: 'Enter' },
        ]
      },
      'duke3d': {
        file: "upload/Duke Nukem 3d-@digitalwalt.zip",
        executable: "./DUKE3D/DUKE3D.EXE",
        title: "Duke Nukem 3D",
        cdnFile: "https://js-dos.com/cdn/upload/Duke Nukem 3d-@digitalwalt.zip",
        keys: [
          { code: -1, key: 'No action' },
          { code: 38, key: 'ArrowUp', text: 'Forward' },
          { code: 40, key: 'ArrowDown', text: 'Back' },
          { code: 37, key: 'ArrowLeft', text: 'Left' },
          { code: 39, key: 'ArrowRight', text: 'Right' },
          { code: 17, key: 'ControlRight', text: 'Fire' },
          { code: 65, key: 'KeyA', text: 'Jump' },
          { code: 13, key: 'Enter' },
        ]
      },
    };
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe, repeatable read operation. The description adds minimal behavioral context beyond what annotations provide - just the scope of 'all available' games. No rate limits, authentication needs, or return format details are mentioned.

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 perfectly concise - a single sentence that directly states the tool's purpose with zero wasted words. It's front-loaded with the core functionality and doesn't include any unnecessary elaboration.

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?

For a simple listing tool with good annotations (read-only, idempotent, non-destructive) and no parameters, the description is adequate but minimal. It lacks information about what the output contains (game names, metadata, etc.) and doesn't provide usage context relative to sibling tools. The annotations cover safety aspects, but the description could add more operational context.

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?

With 0 parameters and 100% schema description coverage, there are no parameters to document. The description appropriately doesn't waste space discussing nonexistent parameters. A baseline of 4 is appropriate for parameterless tools where the schema already fully documents the empty parameter set.

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 verb ('List') and resource ('DOS games'), making the purpose immediately understandable. It specifies 'all available' which provides scope, though it doesn't explicitly differentiate from sibling tools like 'open-dos' or 'close-app' beyond the listing function.

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?

The description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites, when this listing operation is appropriate, or how it relates to sibling tools like 'open-dos' (which might be for launching games) or 'close-app'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/basementstudio/mcp-dos'

If you have feedback or need assistance with the MCP directory API, please join our Discord server