Skip to main content
Glama
simen

VICE C64 Emulator MCP Server

by simen

reset

Restart the Commodore 64 emulator with options for soft reset (preserves memory) or hard reset (clears everything completely).

Instructions

Reset the C64 machine.

Options:

  • hard: If true, performs hard reset (like power cycle). If false, soft reset (like reset button).

A soft reset preserves some memory contents, hard reset clears everything.

Related tools: connect, status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hardNoHard reset (true) vs soft reset (false, default)

Implementation Reference

  • Handler function that executes the reset tool logic: calls underlying client.reset() with hard flag from args, formats MCP response with state metadata or error
    async (args) => {
      try {
        await client.reset(args.hard || false);
        return formatResponse({
          reset: true,
          type: args.hard ? "hard" : "soft",
          message: `${args.hard ? "Hard" : "Soft"} reset performed`,
          hint: "C64 is now at startup. Use status() to check state.",
        });
      } catch (error) {
        return formatError(error as ViceError);
      }
    }
  • Zod input schema defining optional 'hard' boolean parameter for hard/soft reset
    inputSchema: z.object({
      hard: z.boolean().optional().describe("Hard reset (true) vs soft reset (false, default)"),
    }),
  • src/index.ts:531-559 (registration)
    Registration of the 'reset' MCP tool on the McpServer instance
    server.registerTool(
      "reset",
      {
        description: `Reset the C64 machine.
    
    Options:
    - hard: If true, performs hard reset (like power cycle). If false, soft reset (like reset button).
    
    A soft reset preserves some memory contents, hard reset clears everything.
    
    Related tools: connect, status`,
        inputSchema: z.object({
          hard: z.boolean().optional().describe("Hard reset (true) vs soft reset (false, default)"),
        }),
      },
      async (args) => {
        try {
          await client.reset(args.hard || false);
          return formatResponse({
            reset: true,
            type: args.hard ? "hard" : "soft",
            message: `${args.hard ? "Hard" : "Soft"} reset performed`,
            hint: "C64 is now at startup. Use status() to check state.",
          });
        } catch (error) {
          return formatError(error as ViceError);
        }
      }
    );
  • Low-level ViceClient.reset method: constructs 1-byte body (1 for hard reset, 0 for soft) and sends to VICE via sendCommand(Command.Reset)
    async reset(hard = false): Promise<void> {
      const body = Buffer.alloc(1);
      body[0] = hard ? 1 : 0;
      await this.sendCommand(Command.Reset, body);
    }
  • Protocol constant defining Command.Reset as 0xcc (VICE binary monitor command code)
    Reset = 0xcc,
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well by explaining behavioral traits: it details the difference between hard and soft resets (e.g., 'hard reset clears everything', 'soft reset preserves some memory contents'), which is crucial for understanding the tool's impact beyond basic functionality.

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 appropriately sized and front-loaded: it starts with the core purpose, then lists options with clear explanations, and ends with related tools. Every sentence earns its place by adding essential information without redundancy.

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?

Given the tool's moderate complexity (one parameter, no output schema), the description is fairly complete: it covers purpose, parameter semantics, and behavioral context. However, it lacks details on prerequisites (e.g., does the machine need to be connected?) or error conditions, which could be useful given the sibling tools include connection-related ones.

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 description coverage is 100%, so the baseline is 3. The description adds value by explaining the semantics of the 'hard' parameter beyond the schema's description ('Hard reset (true) vs soft reset (false, default)'), clarifying what each option does in practical terms (e.g., 'like power cycle' vs 'like reset button'), elevating the score.

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 verb ('Reset') and resource ('the C64 machine'), making the purpose specific. It distinguishes this tool from siblings like 'connect' or 'status' by focusing on reset functionality rather than connection or status checking.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use the tool (to reset the C64 machine) and mentions related tools ('connect', 'status'), but does not explicitly state when not to use it or compare it to all alternatives among the many siblings listed.

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/simen/vice-mcp'

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