A Model Context Protocol (MCP) server for the Commodore 64 Ultimate — the official modern Commodore 64 computer. Provides tools to interact with the Ultimate's REST API, enabling AI assistants to control the Commodore 64.
The server defines 19 tools with complete JSON Schema input definitions and consistent naming conventions (all start with 'ultimate_' verb prefix). However, descriptions are present but vary widely in quality and actionability. Many lack key context about when to use the tool, what happens when called, and error recovery paths. Parameter descriptions are generally present but terse. No documented output schemas are visible in the source code provided. Error handling is basic, no recovery guidance, no categorization of retryable vs. fatal errors, no suggestions for alternatives. The code shows proper JSON Schema structure with types and required fields, but lacks the LLM-optimized descriptions (50 - 200 chars) needed for A-grade quality. The server handles a coherent domain (C64 Ultimate device control) with clear responsibility boundaries, which is a strength.
Delete a file on the Ultimate device
Get the current connection details for the Ultimate C64 device
Get a portion of C64 memory
Get a screenshot of the C64 screen
Get system information from the Ultimate device
List files on the Ultimate device (in the current directory)
Load a program into C64 memory (does not run it)
Play an Amiga MOD file on the Ultimate
Descriptions lack actionable context. Most descriptions (e.g., 'Get the current version of the Ultimate's REST API', 'Get a screenshot of the C64 screen') do not explain WHEN to use the tool vs. similar tools, what side effects occur, or how to recover from errors. Descriptions average ~60 chars but lack LLM-optimized phrasing (50 - 200 chars with selection context).
No documented output schemas. Source code does not show return type specifications or example responses for any tool. LLMs cannot plan downstream chaining (e.g., after listing files, which field contains the filename?) or validate whether returned data matches expectations. This breaks the tool-chain pattern.
Error handling lacks recovery guidance. The make_request() method returns errors as strings in a generic 'errors' array with no categorization (retryable vs. fatal), no guidance on next steps, and no suggestions for alternatives. E.g., 'HTTP 404' gives the agent nothing to act on.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 53 | <=2025-11-25 | v2 |
Play a SID file on the Ultimate
Read a file from the Ultimate device
Send a reset signal to the C64 (warm reset or cold reset)
Load and run a cartridge file
Upload and run a PRG file. Accepts file path, base64-encoded binary data, or URL to download the PRG file.
Load and run a program on the C64
Send keyboard input to the C64
Set the hostname and port of the Ultimate C64 device
Set a portion of C64 memory
Get the current version of the Ultimate's REST API
Write a file to the Ultimate device
Parameter description brevity. Parameters like 'file' in ultimate_read_file, 'keys' in ultimate_send_keys, and 'path' in ultimate_list_files have minimal or single-sentence descriptions (avg ~40 chars). Best practice is 60 - 100 chars with format constraints, valid ranges, or dependency hints. E.g., 'file' should clarify: 'Absolute path to the file on the Ultimate device (e.g., /games/lode_runner.prg). Use list_files to discover paths.'
Destructive tool (ultimate_delete_file) lacks confirmation/dry-run pattern. The delete_file tool has no confirmation step or dry-run variant. Best practice is to offer a dry-run or require explicit confirmation before irreversible operations to prevent agent mistakes.
Inconsistent parameter naming. ultimate_run_prg_binary uses 'file_path', 'prg_data_base64', 'url', while other file tools use 'file'. This inconsistency forces LLMs to reason about parameter name mappings rather than treating file-like operations uniformly. See naming rule: 'When multiple tools operate on the same resource, their names must make the distinction obvious.'
Missing tool annotations. The code does not show tool registration with destructiveHint, readOnlyHint, or idempotentHint annotations (current MCP spec feature). Tools like ultimate_delete_file, ultimate_reset_c64, and ultimate_set_memory would benefit from explicit annotations to guide LLM behavior.
No pagination or result-limit handling. ultimate_list_files does not document a limit parameter, pagination token, or max result count. If the device has hundreds of files, returning all at once blows the context window. Best practice: add limit (default 20 - 50), offset/cursor, and total_count to response.
Connection state management. The UltimateHandler class is stateful (self.api_base, self.base_url, self.session). While the STDIO server instantiates a single handler per process, distributed or multi-turn scenarios could face stale connection state. Consider stateless per-request connection handling to align with current MCP (2026-07-28) stateless architecture.