Skip to main content
Glama

gc_dolphin_save_state

Save a Dolphin emulator save-state to slot 1-8 using its default hotkey, then copy the state file to a chosen or configured states directory.

Instructions

Save a save-state to slot (1-8) via Shift+F{slot}, then copy it.

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

After saving, the state file is copied into copy_dir (or the server's configured states directory, <data>/states, by default). The result includes copied, state_file and copied_to.

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

Input Schema

NameRequiredDescriptionDefault
slotYes
copy_dirNo
instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/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 burden; it does disclose the key behaviors: input is synthesized as a keyboard hotkey, the state file is then copied, and the default destination is <data>/states. It does not say whether an existing state in the slot is overwritten, what happens if the hotkey is unbound or the emulator is not focused, or whether the operation is reversible/errors out — meaningful gaps for a mutation-style tool.

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?

Front-loaded with the core action and mechanism, then supporting details about binding limits, copy destination, and result fields. Every sentence carries information; only minor unnecessary whitespace/paragraph fragmentation.

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 three-parameter tool with no output schema and no annotations, the definition covers the mechanism, the default path resolution, and even enumerates the result fields (copied, state_file, copied_to). It falls just short on failure modes and instance_id, which an agent would still need to infer.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate, and it does for two of three parameters: slot is bounded to 1-8 with a stated reason, and copy_dir's default resolution (<data>/states) is spelled out. instance_id is left entirely unexplained, which is the only remaining gap.

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?

States a specific verb and resource ('Save a save-state') plus the exact mechanism (Shift+F{slot}) and the follow-up copy behavior. An agent can immediately distinguish this from the sibling gc_dolphin_load_state, which is the inverse operation.

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 usage constraint — only slots 1-8 have a default hotkey binding — and points to gc_dolphin_hotkey_get for verifying bindings. It does not explicitly say when to prefer this over manual config or what to do if a hotkey was rebound, but the context is clear.

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