Skip to main content
Glama
Sign In
PCSX2 MCP

PCSX2 MCP

by snowyegret23
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

find_pattern

Search PCSX2 guest memory for hex patterns, using ?? as wildcard bytes for unknown values.

Instructions

Search guest memory for a hex pattern. Use ?? as a wildcard byte.

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": {
      "pattern": "<pattern>"
    },
    "name": "find_pattern"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
startNo
targetNoee
patternYes
chunk_sizeNo
max_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavioral traits. It only states the search action and wildcard syntax, omitting details about whether memory is modified, performance impact, result sorting, or how overlapping matches are handled.

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 extremely concise (two short sentences) with no extraneous words. However, it sacrifices necessary detail for brevity; a slightly longer description could improve completeness without losing conciseness.

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?

Given 6 parameters, no output schema, and no annotations, the description is severely incomplete. It fails to explain the purpose of most parameters, return format, or any side effects, making it inadequate for an agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must add meaning for all 6 parameters. It only explains the 'pattern' parameter (hex with wildcard), leaving 'start', 'end', 'target', 'chunk_size', and 'max_results' completely unexplained.

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 the tool searches guest memory for a hex pattern, and specifies the wildcard notation '??'. This verb+resource combination is distinct from sibling memory tools like read_memory or dump_memory.

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., reading memory directly or using other search methods). The description does not mention prerequisites, limitations, or typical use cases.

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