Skip to main content
Glama

ppsspp_breakpoint_add

Set a persistent CPU breakpoint at a PSP memory address to halt emulation for reverse engineering or HLE intercepts.

Instructions

PURPOSE: Add a CPU execution breakpoint at the given PSP physical address. Emulation halts when PC reaches that address. USAGE: For RE work and HLE intercepts. Combine with ppsspp_resume + (later) ppsspp_get_registers to inspect state at the breakpoint. BEHAVIOR: Modifies PPSSPP's breakpoint table. The breakpoint persists until removed via ppsspp_breakpoint_remove or PPSSPP restarts. Returns an error if the address isn't executable memory. RETURNS: Single line 'Breakpoint added at ADDR_HEX'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesPSP execution address. Usually in user RAM (0x08800000+) or kernel RAM.

Implementation Reference

  • Schema definition for ppsspp_breakpoint_add tool — defines name, description, inputSchema with required 'address' parameter (integer, minimum 0).
    // ── Breakpoints ────────────────────────────────────────────────────────
    
    {
      name: "ppsspp_breakpoint_add",
      description:
        "PURPOSE: Add a CPU execution breakpoint at the given PSP physical address. Emulation halts when PC reaches that address. " +
        "USAGE: For RE work and HLE intercepts. Combine with ppsspp_resume + (later) ppsspp_get_registers to inspect state at the breakpoint. " +
        "BEHAVIOR: Modifies PPSSPP's breakpoint table. The breakpoint persists until removed via ppsspp_breakpoint_remove or PPSSPP restarts. Returns an error if the address isn't executable memory. " +
        "RETURNS: Single line 'Breakpoint added at ADDR_HEX'.",
      inputSchema: {
        type: "object",
        required: ["address"],
        properties: {
          address: { type: "integer", minimum: 0, description: "PSP execution address. Usually in user RAM (0x08800000+) or kernel RAM." },
        },
        additionalProperties: false,
      },
    },
  • Handler for ppsspp_breakpoint_add — calls PPSSPP's 'cpu.breakpoint.add' RPC with the address, returns a success message.
    case "ppsspp_breakpoint_add": {
      await pp.call("cpu.breakpoint.add", { address: a() });
      return ok(`Breakpoint added at ${addrHex(a())}`);
    }
  • src/tools.ts:405-406 (registration)
    The tool is registered via the TOOLS array and the registerTools function sets up ListToolsRequestSchema and CallToolRequestSchema handlers.
    export function registerTools(server: Server, pp: PpssppClient): void {
      server.setRequestHandler(ListToolsRequestSchema, async () => ({ tools: TOOLS }));
Behavior5/5

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

With no annotations, the description fully discloses key behaviors: modifies PPSSPP's breakpoint table, persistence until removal or restart, error on non-executable memory, and expected return message. This covers mutation and side effects comprehensively.

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 with labeled sections (PURPOSE, USAGE, BEHAVIOR, RETURNS). Every sentence adds value with no superfluous content, achieving high efficiency.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a single parameter and no output schema, the description covers all necessary context: purpose, usage guidance, behavior, and return format. No gaps are present.

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?

The schema already provides 100% coverage with a detailed description for the 'address' parameter. The tool description simply restates 'PSP physical address' but adds no new semantic details beyond the schema, meriting a baseline score of 3.

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 action 'Add a CPU execution breakpoint' and specifies the trigger condition 'Emulation halts when PC reaches that address.' It distinguishes from siblings by focusing on addition rather than listing or removal.

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?

Explicitly states usage for 'RE work and HLE intercepts' and provides a concrete combination 'Combine with ppsspp_resume + (later) ppsspp_get_registers to inspect state at the breakpoint.' This guides appropriate tool selection.

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/dmang-dev/mcp-ppsspp'

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