Skip to main content
Glama

gc_dolphin_toggle_pause

Toggles a Dolphin emulator instance's pause state, letting you pause before inspecting memory or screen and resume afterward.

Instructions

Toggle the emulator's pause state (Dolphin's Toggle Pause hotkey, F10).

Use this to pause a game (e.g. before inspecting memory or screen), then resume. When paused, gc_dolphin_step_frame advances exactly one frame.

This injects a keystroke into the instance's X display via xdotool, so it requires the xvfb capture backend and xdotool installed. On a headless --batch instance Dolphin's [Input] BackgroundInput = True keeps the input gate open so the hotkey is received without window focus.

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_dolphin_toggle_pause"
  }
}

Input Schema

NameRequiredDescriptionDefault
instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and does substantial work: it discloses that the action is implemented by injecting a keystroke via xdotool, that the xvfb capture backend and xdotool must be present, and that --batch instances need [Input] BackgroundInput = True. What it does not disclose is whether the call reports the resulting pause state, which matters for a toggle-style operation.

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 primary behavior and the use case are front-loaded, with the xdotool/Xvfb prerequisites correctly relegated to a second paragraph. The paragraph on headless BackgroundInput is dense but earns its place as a real operational caveat; there is minimal filler.

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

Completeness4/5

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

With no annotations and no output schema, the description supplies purpose, prerequisites, and the interaction with step-frame, which is enough to call it correctly. The remaining gap is the return contract for a state-dependent toggle, which would let an agent verify state without a separate query.

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% for the single instance_id parameter, so the description must compensate, and it only partially does by referring to 'the instance's X display'. This implies instance_id selects an emulator instance but gives no format, source tool, or validation detail beyond that inference.

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 names a specific verb and resource ('Toggle the emulator's pause state'), anchors it to a known mechanic (Dolphin's Toggle Pause hotkey, F10), and explicitly distinguishes it from the sibling gc_dolphin_step_frame, which only advances while paused. An agent can identify this tool's role without opening any schema.

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

Usage Guidelines4/5

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

It gives a concrete when-to-use scenario ('pause a game, e.g. before inspecting memory or screen, then resume') and clarifies the division of labor with gc_dolphin_step_frame. It stops short of stating exclusions (e.g. don't use outside an xvfb-backed instance), so it is strong guidance rather than a complete when/when-not rule set.

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