Skip to main content
Glama
Sign In
PCSX2 MCP

PCSX2 MCP

by snowyegret23
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

remove_debug_breakpoint

Remove a specific breakpoint from the PCSX2 emulator debugger by providing its memory address.

Instructions

Remove a PCSX2 debugger breakpoint.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>"
    },
    "name": "remove_debug_breakpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetNoee
addressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.8/5.0
Behavior1/5

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

With no annotations and a single-sentence description, no behavioral traits are disclosed. It does not mention what happens if the breakpoint doesn't exist, whether it affects execution, or any prerequisites.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While the description is concise (one sentence), it is under-informative. The space is not used efficiently to convey necessary details, making it more of a tautology than a useful description.

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

Completeness1/5

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

For a tool with 2 parameters and no output schema, the description is severely lacking. It does not explain the effect, valid values for 'target', or how to specify the address, leaving the agent with insufficient context to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the description adds no explanation for the parameters 'target' and 'address'. The agent must infer that 'target' defaults to 'ee' (Emotion Engine) and 'address' can be integer or string, but no format guidance is given.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the verb 'Remove' and resource 'a PCSX2 debugger breakpoint', but it does not distinguish from the sibling tool 'remove_breakpoint', which likely has similar purpose. This lack of differentiation reduces clarity.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'remove_breakpoint' or 'clear_debug_breakpoints'. The agent is left to infer the appropriate context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools