Skip to main content
Glama
simen

VICE C64 Emulator MCP Server

by simen

status

Check VICE emulator connection status and verify if emulation is running or paused before executing debugging commands.

Instructions

Get current VICE connection and emulation state.

Returns connection status, whether emulation is running or paused, and host/port if connected.

Use this to:

  • Check if you're connected before running other commands

  • See if emulation is running or stopped (e.g., at a breakpoint)

  • Verify connection details

Related tools: connect, disconnect

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the 'status' tool logic. Retrieves the VICE client state and formats a response with connection status, running state, host/port if connected, and contextual hints.
    async () => {
      const state = client.getState();
      return formatResponse({
        connected: state.connected,
        running: state.running,
        ...(state.connected && {
          host: state.host,
          port: state.port,
        }),
        hint: state.connected
          ? state.running
            ? "VICE is running. Use setBreakpoint() + continue() to pause at a specific point, or step() to execute one instruction."
            : "VICE is paused. Use continue() to resume or step() to execute one instruction."
          : "Not connected. Use connect() to establish connection to VICE.",
      });
    }
  • src/index.ts:94-124 (registration)
    The registration of the 'status' tool with the MCP server, including name, description, and reference to the inline handler function. No input schema defined as the tool takes no parameters.
    server.registerTool(
      "status",
      {
        description: `Get current VICE connection and emulation state.
    
    Returns connection status, whether emulation is running or paused, and host/port if connected.
    
    Use this to:
    - Check if you're connected before running other commands
    - See if emulation is running or stopped (e.g., at a breakpoint)
    - Verify connection details
    
    Related tools: connect, disconnect`,
      },
      async () => {
        const state = client.getState();
        return formatResponse({
          connected: state.connected,
          running: state.running,
          ...(state.connected && {
            host: state.host,
            port: state.port,
          }),
          hint: state.connected
            ? state.running
              ? "VICE is running. Use setBreakpoint() + continue() to pause at a specific point, or step() to execute one instruction."
              : "VICE is paused. Use continue() to resume or step() to execute one instruction."
            : "Not connected. Use connect() to establish connection to VICE.",
        });
      }
    );
  • The ViceClient.getState() method, which provides the connection and emulation state (connected, running, host, port) used directly by the status tool handler.
    getState(): ConnectionState {
      return { ...this.state };
    }
  • The formatResponse helper function used by the status handler (and other tools) to wrap the response data with _meta state information in a standardized MCP content format.
    function formatResponse(data: object) {
      const state = client.getState();
      return {
        content: [
          {
            type: "text" as const,
            text: JSON.stringify(
              {
                ...data,
                _meta: {
                  connected: state.connected,
                  running: state.running,
                  ...(state.connected && { host: state.host, port: state.port }),
                },
              },
              null,
              2
            ),
          },
        ],
      };
    }
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 effectively describes what the tool returns ('connection status', 'whether emulation is running or paused', 'host/port if connected'), which is appropriate for a read-only status tool. However, it doesn't mention potential errors, latency, or rate limits.

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 well-structured and front-loaded with the core purpose, followed by specific usage guidelines and related tools. Every sentence adds value without redundancy, making it efficient and easy to parse.

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?

For a 0-parameter status tool with no annotations or output schema, the description provides good context about what information is returned and when to use it. However, without an output schema, it could benefit from more detail about the exact structure of the returned data (e.g., specific fields, data types).

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 the baseline is 4. The description appropriately doesn't discuss parameters since none exist, focusing instead on the tool's purpose and usage.

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 ('Get current VICE connection and emulation state') and resources ('connection status', 'emulation state', 'host/port'). It distinguishes itself from siblings by focusing on status retrieval rather than connection management or execution control.

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 provides explicit usage guidelines with a bulleted list of when to use this tool ('Check if you're connected before running other commands', 'See if emulation is running or stopped', 'Verify connection details'). It also mentions related tools (connect, disconnect) for context, though it doesn't explicitly state when not to use it.

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