PCSX2 MCP

Overview Schema Source Related Servers Discussions Admin

disassemble

Decode guest instructions at a given memory address for the specified CPU target (EE, IOP, etc.) with configurable count. Use to analyze emulator code execution.

Instructions

Disassemble guest instructions using PCSX2's native debugger disassembler.

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

Input Schema

Name	Required	Default
`count`	No
`target`	No	ee
`address`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 27, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations exist, so the description must disclose behavioral traits. It only states the basic action without describing side effects, return format, or constraints (e.g., address range, target options). Minimal transparency.

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 a single sentence with no superfluous words. However, it is too brief, omitting crucial details about parameters and usage that would improve structure.

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 the complexity of a disassembly tool and the lack of output schema, the description is incomplete. It does not specify what the tool returns (e.g., formatted assembly lines) or how to interpret results.

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 (count, target, address). No meaning added beyond the schema's property names and types. The agent must guess the role of each parameter.

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?

The description clearly states it disassembles guest instructions using PCSX2's native debugger disassembler. The verb 'disassemble' and resource 'guest instructions' are specific, and the method is named. It distinguishes from sibling tools like read_memory or get_registers.

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 vs alternatives (e.g., read_memory, evaluate). No prerequisites or context for usage are provided, leaving the agent to infer from the name alone.

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