Skip to main content
Glama
Sign In
PCSX2 MCP

PCSX2 MCP

by snowyegret23
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

save_state_slot

Save game progress to a specific savestate slot in PCSX2 for quick reloading.

Instructions

Save a PCSX2 savestate slot synchronously.

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": {
      "slot": "<slot>"
    },
    "name": "save_state_slot"
  }
}

Input Schema

NameRequiredDescriptionDefault
slotYes
targetNoee

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It only reveals that the save is synchronous, but omits side effects (e.g., overwriting existing saves), failure modes, or whether it requires a specific state (e.g., paused).

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

Conciseness4/5

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

The description is a single focused sentence with no extraneous words. It is efficient but could be slightly expanded to include parameter details without becoming verbose.

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

Completeness2/5

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

Given 0% schema coverage, no output schema, and no annotations, the description is insufficient. It fails to explain the slot range, target options, return behavior, or error conditions, which are necessary for safe 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?

No description is given for the 'slot' or 'target' parameters. Schema coverage is 0%, so the description adds no value beyond the schema field names. An agent using this tool would have to guess the meaning and valid values.

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 action ('Save') and the resource ('PCSX2 savestate slot'), and the adverb 'synchronously' adds a behavioral nuance that helps distinguish it from potentially asynchronous operations. However, it doesn't explain what a 'slot' is in context, leaving some ambiguity for unfamiliar agents.

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 'load_state_slot' or 'save_state_file'. There is no mention of prerequisites (e.g., emulation must be running) or when synchronous behavior is required.

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