Skip to main content
Glama
simen

VICE C64 Emulator MCP Server

by simen

continue

Resume C64 emulator execution after debugging pauses or breakpoints to continue program analysis and testing.

Instructions

Resume C64 execution after a breakpoint or pause.

Starts the emulator running until the next breakpoint, manual stop, or error.

Related tools: step, status, setBreakpoint

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler implementation in ViceClient that sends the VICE Exit command (0xaa) to resume emulation execution
    async continue(): Promise<void> {
      // Exit command (0xaa) resumes execution
      await this.sendCommand(Command.Exit);
      this.state.running = true;
      this.stoppedConfirmed = false; // Need to re-confirm stopped state after resume
    }
  • src/index.ts:449-470 (registration)
    MCP server registration of the 'continue' tool, including description and handler lambda
    server.registerTool(
      "continue",
      {
        description: `Resume C64 execution after a breakpoint or pause.
    
    Starts the emulator running until the next breakpoint, manual stop, or error.
    
    Related tools: step, status, setBreakpoint`,
      },
      async () => {
        try {
          await client.continue();
          return formatResponse({
            resumed: true,
            message: "Execution resumed",
            hint: "Use status() to check if execution stopped (e.g., at breakpoint)",
          });
        } catch (error) {
          return formatError(error as ViceError);
        }
      }
    );
  • Tool metadata including description for the 'continue' MCP tool (no input schema as tool takes no parameters)
      {
        description: `Resume C64 execution after a breakpoint or pause.
    
    Starts the emulator running until the next breakpoint, manual stop, or error.
    
    Related tools: step, status, setBreakpoint`,
      },
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 of behavioral disclosure. It explains the tool's behavior ('starts the emulator running until the next breakpoint, manual stop, or error'), which covers execution flow and termination conditions. However, it doesn't mention potential side effects like memory changes or performance implications, leaving some gaps.

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 front-loaded with the core purpose in the first sentence, followed by behavioral details and related tools. Each sentence adds value without redundancy, and the structure is efficient with no wasted words.

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 simplicity (0 parameters, no output schema, no annotations), the description is largely complete for its purpose. It explains what the tool does, when to use it, and related tools. However, without annotations or output schema, it could benefit from more details on return values or error conditions, slightly reducing completeness.

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 tool has 0 parameters with 100% schema description coverage, so no parameter information is needed. The description appropriately doesn't discuss parameters, earning a baseline score of 4 for not adding unnecessary details 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 tool's purpose with specific verbs ('resume', 'starts') and identifies the resource ('C64 execution'). It distinguishes from siblings by specifying it's for continuing after a breakpoint or pause, unlike tools like 'step' (single-step) or 'reset' (restart).

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool ('after a breakpoint or pause') and lists related alternatives ('step, status, setBreakpoint'), providing clear guidance on context and sibling differentiation without misleading information.

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