Skip to main content
Glama
simen

VICE C64 Emulator MCP Server

by simen

deleteBreakpoint

Remove a debugging breakpoint in the VICE C64 emulator by specifying its ID to control program execution flow during assembly code analysis.

Instructions

Delete a breakpoint by its ID.

Use listBreakpoints to see current breakpoint IDs.

Related tools: setBreakpoint, listBreakpoints

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
breakpointIdYesBreakpoint ID from setBreakpoint

Implementation Reference

  • MCP tool handler for 'deleteBreakpoint': extracts breakpointId from args, calls the underlying ViceClient.deleteBreakpoint method, formats success response with metadata or error response.
    async (args) => {
      try {
        await client.deleteBreakpoint(args.breakpointId);
        return formatResponse({
          success: true,
          deletedId: args.breakpointId,
          message: `Breakpoint ${args.breakpointId} deleted`,
        });
      } catch (error) {
        return formatError(error as ViceError);
      }
    }
  • Zod input schema for deleteBreakpoint tool requiring a single numeric 'breakpointId' parameter.
    inputSchema: z.object({
      breakpointId: z.number().describe("Breakpoint ID from setBreakpoint"),
    }),
  • src/index.ts:607-631 (registration)
    Registration of the MCP 'deleteBreakpoint' tool with McpServer, including description, input schema, and handler function.
    server.registerTool(
      "deleteBreakpoint",
      {
        description: `Delete a breakpoint by its ID.
    
    Use listBreakpoints to see current breakpoint IDs.
    
    Related tools: setBreakpoint, listBreakpoints`,
        inputSchema: z.object({
          breakpointId: z.number().describe("Breakpoint ID from setBreakpoint"),
        }),
      },
      async (args) => {
        try {
          await client.deleteBreakpoint(args.breakpointId);
          return formatResponse({
            success: true,
            deletedId: args.breakpointId,
            message: `Breakpoint ${args.breakpointId} deleted`,
          });
        } catch (error) {
          return formatError(error as ViceError);
        }
      }
    );
  • ViceClient helper method implementing breakpoint deletion by sending VICE CheckpointDelete command and updating local checkpoint tracking.
    async deleteBreakpoint(checkpointId: number): Promise<void> {
      const body = Buffer.alloc(4);
      body.writeUInt32LE(checkpointId, 0);
      await this.sendCommand(Command.CheckpointDelete, body);
    
      // Remove from local tracking
      this.checkpoints.delete(checkpointId);
    }
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that this is a destructive operation ('Delete'), but lacks details on permissions, side effects, error handling, or confirmation requirements. For a mutation tool with zero annotation coverage, this leaves significant behavioral 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 highly concise and well-structured, with three sentences that each serve a distinct purpose: stating the action, providing usage prerequisites, and listing related tools. There is no wasted text, and information is front-loaded effectively.

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 complexity (simple deletion with one parameter) and the lack of annotations or output schema, the description is reasonably complete. It covers purpose, usage, and parameters adequately, though it could benefit from more behavioral details like error conditions or success indicators.

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?

Schema description coverage is 100%, with the parameter 'breakpointId' fully documented in the schema. The description adds minimal value by referencing 'Breakpoint ID from setBreakpoint', which slightly clarifies the source but doesn't provide additional syntax or format details beyond the schema's description.

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 specific action ('Delete') and resource ('a breakpoint by its ID'), distinguishing it from sibling tools like setBreakpoint, listBreakpoints, and toggleBreakpoint. It explicitly names the verb and target, leaving no ambiguity about its function.

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 guidance on when to use this tool ('Delete a breakpoint by its ID') and when to use alternatives ('Use listBreakpoints to see current breakpoint IDs'), including naming related tools (setBreakpoint, listBreakpoints). This clearly defines the context and prerequisites for invocation.

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