Skip to main content
Glama

gc_dolphin_step_frame

Advance a paused Dolphin emulator by exactly one video frame using its Frame Advance hotkey, enabling precise TAS frame-by-frame control.

Instructions

Advance exactly one frame when the emulator is paused.

Sends Dolphin's Frame Advance hotkey. Unlike Step Into (a CPU-debugger step), Frame Advance steps one video frame, which is what a TAS tool wants.

The instance config binds Frame Advance to F8 by default (see gc_dolphin_hotkey_get/gc_dolphin_hotkey_set). If it is unbound this tool returns ok=False and no frame advances.

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

Input Schema

NameRequiredDescriptionDefault
instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the mechanism (sends the Frame Advance hotkey), the default binding (F8), and the concrete failure mode (returns ok=False and no frame advances if unbound). It does not say what happens when invoked while unpaused, which is the one behavioral gap.

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 core action and precondition are front-loaded in the first sentence, and the Step Into contrast follows immediately. The hotkey-binding paragraph is useful but runs slightly long for a one-parameter tool and could be tightened.

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?

For a one-parameter mutation tool with no annotations and no output schema, the definition covers mechanism, prerequisite, failure result, and the config dependency that affects success. The missing piece is the undocumented instance_id parameter and any note about preconditions being enforced rather than assumed.

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% for the single parameter, so the description should explain instance_id but never mentions it at all. The name is conventional for this server, but nothing in the definition tells the agent what value to supply or what happens for an unknown instance.

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 gives a specific verb and resource ('Advance exactly one frame') plus the precondition ('when the emulator is paused'), and it explicitly distinguishes itself from 'Step Into' by noting that this steps one video frame rather than a CPU-debugger step. An agent can identify the operation without opening the 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 states the operative context (emulator must be paused) and the TAS-oriented intent, which is real when-to-use guidance. It stops short of saying what to do instead if the emulator is running or naming a sibling to pair with for pausing, so the exclusions are implied rather than explicit.

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