Skip to main content
Glama
simen

VICE C64 Emulator MCP Server

by simen

listBreakpoints

Display all active debugging breakpoints in the VICE C64 emulator session, showing IDs, addresses, and status for program analysis.

Instructions

List all active breakpoints.

Shows breakpoint IDs, addresses, and status for all breakpoints set in this session.

Note: This tracks breakpoints set through this MCP session. Breakpoints set through VICE's built-in monitor may not appear.

Related tools: setBreakpoint, deleteBreakpoint

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'listBreakpoints': calls client.listBreakpoints(), handles empty list case, formats breakpoints data with addresses, status, and hints into MCP response structure.
    async () => {
      const breakpoints = client.listBreakpoints();
    
      if (breakpoints.length === 0) {
        return formatResponse({
          count: 0,
          breakpoints: [],
          hint: "No breakpoints set. Use setBreakpoint() to add one.",
        });
      }
    
      return formatResponse({
        count: breakpoints.length,
        breakpoints: breakpoints.map((bp) => ({
          id: bp.id,
          address: {
            value: bp.startAddress,
            hex: `$${bp.startAddress.toString(16).padStart(4, "0")}`,
          },
          enabled: bp.enabled,
          temporary: bp.temporary,
        })),
        hint: `${breakpoints.length} breakpoint(s) active. Use deleteBreakpoint(id) to remove.`,
      });
    }
  • src/index.ts:634-670 (registration)
    Registration of the 'listBreakpoints' MCP tool with server.registerTool, providing tool name, description, and handler function.
    server.registerTool(
      "listBreakpoints",
      {
        description: `List all active breakpoints.
    
    Shows breakpoint IDs, addresses, and status for all breakpoints set in this session.
    
    Note: This tracks breakpoints set through this MCP session. Breakpoints set through VICE's built-in monitor may not appear.
    
    Related tools: setBreakpoint, deleteBreakpoint`,
      },
      async () => {
        const breakpoints = client.listBreakpoints();
    
        if (breakpoints.length === 0) {
          return formatResponse({
            count: 0,
            breakpoints: [],
            hint: "No breakpoints set. Use setBreakpoint() to add one.",
          });
        }
    
        return formatResponse({
          count: breakpoints.length,
          breakpoints: breakpoints.map((bp) => ({
            id: bp.id,
            address: {
              value: bp.startAddress,
              hex: `$${bp.startAddress.toString(16).padStart(4, "0")}`,
            },
            enabled: bp.enabled,
            temporary: bp.temporary,
          })),
          hint: `${breakpoints.length} breakpoint(s) active. Use deleteBreakpoint(id) to remove.`,
        });
      }
    );
  • ViceClient method that returns only execution-type checkpoints (breakpoints) from the local checkpoints Map, used by the MCP tool handler.
    listBreakpoints(): CheckpointInfo[] {
      return Array.from(this.checkpoints.values()).filter((cp) => cp.type === "exec");
    }
  • Type definitions for CheckpointInfo (and alias BreakpointInfo) used to type the breakpoints data returned by listBreakpoints.
    export interface CheckpointInfo {
      id: number;
      startAddress: number;
      endAddress: number;
      enabled: boolean;
      temporary: boolean;
      type: CheckpointType;
    }
    
    // Keep for backwards compatibility
    export type BreakpointInfo = CheckpointInfo;
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool lists breakpoints (implying read-only behavior) and specifies scope (breakpoints set in this session vs. VICE's monitor). However, it doesn't mention potential side effects, error conditions, or response format details that would be helpful for an agent.

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. Each sentence adds value: the first states what it does, the second provides details on what's shown, the third clarifies scope limitations, and the fourth links to related tools. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 reasonably complete for a read-only listing operation. It covers purpose, scope, and related tools. However, without annotations or output schema, it could benefit from more detail on return format or error handling to be fully comprehensive.

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 input schema has 0 parameters with 100% coverage, so the schema fully documents the lack of parameters. The description appropriately doesn't discuss parameters, maintaining focus on the tool's purpose and behavior. A baseline of 4 is applied for zero-parameter tools.

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 verb ('List') and resource ('all active breakpoints'), and distinguishes it from siblings by specifying it shows breakpoints set in this MCP session. It explicitly mentions related tools (setBreakpoint, deleteBreakpoint) for context.

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 on when to use this tool (to list breakpoints set in this session) and includes a note about limitations (breakpoints set through VICE's built-in monitor may not appear). However, it doesn't explicitly state when NOT to use it or compare it to all potential alternatives among siblings.

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