Skip to main content
Glama

gc_dolphin_load_state

Load a Dolphin emulator save-state from slots 1-8 using the default F-key hotkey to restore a previous gameplay session.

Instructions

Load a save-state from slot (1-8) via F{slot}.

Only slots 1-8 have a Dolphin default hotkey binding (see gc_dolphin_hotkey_get).

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>",
      "slot": "<slot>"
    },
    "name": "gc_dolphin_load_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
slotYes
instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the mechanism (it sends F{slot}) and the slot range limit. It says nothing about prerequisites (is a ROM running?), what happens if no save-state exists in that slot, or whether the call returns anything.

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?

Two short sentences, front-loaded with the action and slot range. The mechanism and cross-reference earn their place. Minor cost is the doubled backtick markup, which adds no meaning.

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?

For a two-parameter mutation with no annotations and no output schema, the description is adequate but thin. The slot side is well covered, but instance_id and failure behavior are absent, which leaves real gaps for an agent invoking this blind.

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 fill the gap. It explains slot thoroughly, giving the 1-8 range and the F{slot} mapping. It says nothing about instance_id, leaving half the parameters undocumented anywhere.

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?

Uses a specific verb and resource: "Load a save-state from ``slot``". Distinguishes it implicitly from gc_dolphin_save_state and explicitly from hotkey-based tooling. It never names the save counterpart, so sibling differentiation is only partial.

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?

States a hard constraint: only slots 1-8 have a default hotkey binding, and it points to gc_dolphin_hotkey_get for binding details. It doesn't say when to prefer this over hotkey_set or what to do if the slot is empty.

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