PCSX2 MCP

Overview Schema Source Related Servers Discussions Admin

start_rewind_capture

Begin periodic capture of savestates into a ring buffer, enabling rewind functionality during emulation. Configure slots, target (EE or IOP), interval, and optional directory.

Instructions

Start periodic savestate capture into a ring buffer for rewind.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "start_rewind_capture"
  }
}

Input Schema

Name	Required	Default
`slots`	No
`target`	No	ee
`directory`	No
`rewind_id`	No	default
`interval_sec`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 27, 2026

TDQS

B3.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries full burden. It explains the basic behavior: periodic captures are stored in a ring buffer for rewind. However, it fails to disclose details like overwrite behavior, buffer-full handling, or effect on existing savestates.

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?

Single sentence with 10 words. Extremely concise and front-loaded with the action, 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 no annotations, output schema, or parameter descriptions, the tool's purpose is clear but lacks details on how the ring buffer works, default behaviors, and side effects. It is minimally adequate for a simple tool but incomplete for nuanced use.

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 description coverage is 0% and the description adds no value for any of the 5 parameters. Parameter names like 'Slots', 'Target', 'Directory', 'Rewind Id', and 'Interval Sec' are only marginally self-explanatory without further context.

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?

Description clearly states 'Start periodic savestate capture into a ring buffer for rewind.' It specifies the verb (start), resource (periodic savestate capture), and purpose (rewind). This distinguishes it from sibling tools like save_state_slot or load_state_slot.

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 on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or when not to use it.

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