Skip to main content
Glama

gc_dolphin_hotkey_set

Sets or clears a Dolphin emulator hotkey binding while preserving all existing bindings and default hotkeys. Use it to bind a key or key combination to a control such as Toggle Pause or Frame Advance.

Instructions

Set (or clear) a Dolphin emulator hotkey binding.

key is the Hotkeys.ini key <group>/<control>. expression is the binding in Dolphin input syntax, e.g. F8 for a single key or @(Shift+F8) for a combination. Pass expression="" to unbind it.

Dolphin loads Hotkeys.ini all-or-nothing, so this preserves every existing binding and the built-in default set, then applies key. A running instance may need a restart for the change to take effect. This is Dolphin-only.

Common keys (see gc_dolphin_* tools): General/Toggle Pause, Frame Advance/Frame Advance, Save State/Save State Slot 1..8, Load State/Load State Slot 1..8.

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>",
      "key": "<key>",
      "expression": "<expression>"
    },
    "name": "gc_dolphin_hotkey_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
expressionYes
instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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 real work: it explains that Hotkeys.ini loads all-or-nothing, that existing bindings and built-in defaults are preserved, and that a running instance may need a restart. It stops short of saying what happens on an invalid expression or whether the write is reversible/backed up.

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?

Front-loaded with the verb and resource, then layered: key format, expression syntax, side-effect guarantees, restart caveat, then example keys. Every paragraph adds information an agent would otherwise have to guess, and nothing is repeated from the schema.

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 3-parameter mutation with no annotations and no output schema, the description covers the risky parts well (preservation of other bindings, restart requirement). The two remaining gaps are the undocumented `instance_id` and the absence of any statement about the success/error response shape.

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: `key` is documented as a Hotkeys.ini `<group>/<control>` path with concrete examples, and `expression` gets full syntax guidance including the empty-string unbind case. `instance_id` is never explained, which keeps it off a 5.

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?

States a specific verb and resource: 'Set (or clear) a Dolphin emulator hotkey binding.' The scope qualifier 'This is Dolphin-only' plus the mention of gc_dolphin_* tools places it clearly among the emulator-config siblings, though it never names gc_dolphin_hotkey_get as the read counterpart the way a 5 would.

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?

Gives the one explicit when-case that matters (pass expression="" to unbind) and points at gc_dolphin_* tools for discovering valid keys. It does not say when to prefer this over gc_dolphin_config_set, nor instruct the agent to read current bindings via gc_dolphin_hotkey_get first, so routing is implied rather than stated.

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