Commodore 64 Ultimate Computer MCP Server

by xphileby

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

run_crt_file

Load and execute Commodore 64 cartridge files to run games or applications on C64 Ultimate Computer devices.

Instructions

Start a cartridge file from filesystem

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": {
      "file": "<file>"
    },
    "name": "run_crt_file"
  }
}

Input Schema

Name	Required	Description	Default
`file`	Yes	Path to the CRT file on the device

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 11, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Start') but doesn't explain what this entails—whether it loads and executes the cartridge, affects machine state, requires specific conditions, or has side effects like resetting the system. This leaves significant gaps for an agent to understand the tool's behavior.

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, efficient sentence with no wasted words. It front-loads the key action and resource, making it easy to parse quickly.

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?

Given the complexity of running a cartridge file (likely involving machine state changes) and the lack of annotations and output schema, the description is insufficient. It doesn't address what happens after starting, potential errors, or interactions with other tools, leaving the agent with incomplete context for safe and effective use.

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?

The input schema has 100% description coverage, with the single parameter 'file' documented as 'Path to the CRT file on the device'. The description adds no additional meaning beyond this, as it only mentions 'from filesystem' which is implied by the schema. Baseline 3 is appropriate since the schema adequately covers the parameter.

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 ('Start') and resource ('a cartridge file from filesystem'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'run_crt_upload' which likely serves a similar function but from uploaded data rather than filesystem.

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 such as 'run_crt_upload' or other cartridge/PRG-related tools. The description lacks context about prerequisites, constraints, or typical use cases.

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