Skip to main content
Glama

gc_capture_screenshot

Capture the current frame of a GameCube emulator instance as a PNG, returning the saved file path and optional base64-encoded image data.

Instructions

Capture the current frame of an instance to a PNG.

Returns the path to the saved PNG, and optionally base64-encoded image data.

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": {
      "instance_id": "<instance_id>"
    },
    "name": "gc_capture_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameNo
instance_idYes
include_base64No

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It does valuable work by describing the return value (a PNG path plus optional base64 data), but it says nothing about side effects such as writing to disk, whether an existing file at the given filename is overwritten, or what happens if the instance is not running.

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

Conciseness5/5

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

Two short sentences, front-loaded with the core action and followed by the return contract. No filler wording; every sentence carries information.

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

Completeness3/5

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

The absence of an output schema makes the return-value sentence essential, and it is present. However, for a three-parameter, zero-coverage, annotation-free tool that writes a file, the description leaves meaningful gaps around filename handling and required instance state.

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

Parameters3/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 compensate for all three parameters. It hints at the filename parameter (the PNG is 'saved') and clearly maps to include_base64 ('optionally base64-encoded image data'), but filename defaulting, path resolution, and overwrite behavior are unaddressed, and instance_id is left entirely to the schema title.

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 states a specific verb and resource: 'Capture the current frame of an instance to a PNG.' That is clearly distinguishable from sibling tools such as gc_dolphin_save_state or gc_controller_get_state. It stops short of explicitly differentiating itself from those siblings, so it is clear but not maximally sharp.

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?

There is no guidance on when to use this tool versus alternatives, and no prerequisites such as whether the instance must be running or whether a capture backend must be configured first (despite gc_capture_configure/gc_capture_backends existing as siblings). Usage is only implied by the word 'current frame'.

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