PCSX2 MCP

Overview Schema Source Related Servers Discussions Admin

read_memory

Read guest memory from a PCSX2 emulated game, specifying address and length, and receive data in hex, base64, ascii, hexdump, or u32_array format.

Instructions

Read guest memory as hex, base64, ascii, hexdump, or u32_array.

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>",
      "length": "<length>"
    },
    "name": "read_memory"
  }
}

Input Schema

Name	Required	Default
`length`	Yes
`target`	No	ee
`address`	Yes
`as_format`	No	hex

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 27, 2026

TDQS

C2.4/5.0

Behavior2/5

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

No annotations exist, and the description only mentions reading. It does not disclose side effects, error behavior (e.g., invalid address), or whether it modifies state. Lacks transparency for a potentially destructive operation.

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

Conciseness3/5

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

The description is extremely concise (single clause) but sacrifices necessary detail. It front-loads the verb and resource but leaves critical parameter info out, making it insufficient.

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 4 parameters, no output schema, and no annotations, the description fails to provide complete context. Missing error handling, format details, and usage scenarios, making it hard for an AI agent to use 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 description coverage is 0%, and the description does not explain any parameter. Key aspects like what 'address' means (absolute/virtual), 'length' units, 'target' purpose, and 'as_format' options are undefined.

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 it reads guest memory and lists specific output formats (hex, base64, etc.), distinguishing it from siblings like read_string or disassemble. However, it could be more precise about the context ('guest memory' in emulation).

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 (e.g., read_string for strings, memory_diff for comparisons). No prerequisites or context provided.

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