PCSX2 MCP

Overview Schema Source Related Servers Discussions Admin

set_watchpoint

Set a memory watchpoint in PCSX2 to monitor reads, writes, or execution at a specified address, with options for size, condition, and break action.

Instructions

Set a PCSX2 debugger memory watchpoint.

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": "set_watchpoint"
  }
}

Input Schema

Name	Required	Default
`kind`	No	write
`size`	No
`action`	No	break
`target`	No	ee
`address`	Yes
`condition`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 27, 2026

TDQS

C2.1/5.0

Behavior1/5

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

The description gives no behavioral details beyond the name. It does not mention side effects, required state (e.g., must be paused), or what happens when triggered. With zero annotations, this is a major gap.

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?

The description is extremely concise (one sentence), but at the cost of necessary detail. It is not well-structured for an agent to understand usage.

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?

With 6 parameters, no output schema, and no annotations, the description is severely under-informative. It fails to provide a complete picture for correct tool selection and invocation.

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?

The input schema has 6 parameters with no descriptions, and the tool description adds zero information about them. Parameter names (kind, size, action, target, address, condition) are left to inference, making correct invocation difficult.

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

Purpose4/5

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

The description clearly states the tool sets a memory watchpoint in the PCSX2 debugger, distinguishing it from sibling tools like set_breakpoint or remove_watchpoint. However, it could provide more context about what a watchpoint does.

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 set_breakpoint, or what prerequisites are needed (e.g., paused emulator). The description lacks usage context.

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