Skip to main content
Glama
Sign In
PCSX2 MCP

PCSX2 MCP

by snowyegret23
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

take_screenshot

Save the current PCSX2 render frame as an image file, even when the emulator window is minimized or inactive.

Instructions

Save the current PCSX2 render frame to an image file, even if the emulator window is inactive or minimized.

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

Input Schema

NameRequiredDescriptionDefault
targetNoee
file_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 discloses a key behavior (works while minimized) but omits other relevant traits such as file format, whether the emulator must be running, or error handling. The behavioral disclosure is adequate but not comprehensive.

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 unnecessary words. However, it sacrifices essential information for brevity, especially regarding parameters. It is concise but under-informative.

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?

With two parameters, no output schema, and no annotations, the description should provide more comprehensive guidance. It lacks parameter explanations, return value details, and file format information. The tool's main purpose is clear, but operational details are missing, reducing completeness for an AI agent.

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 tool description does not explain the two parameters ('target' and 'file_path'). The meaning of 'target' (default 'ee') is unclear, and the behavior of 'file_path' (default null) is not described. This severely hinders correct invocation.

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?

Clearly states the verb 'save' and resource 'current PCSX2 render frame'. The description includes a unique behavioral note (works even when inactive/minimized), distinguishing it from sibling tools which focus on debugging, state management, and memory operations. No ambiguity about what the tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is for capturing frames regardless of window state, but provides no explicit guidance on when to use it versus alternatives, no prerequisites, and no conditions where it might not work. The context is clear but lacks depth.

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