Skip to main content
Glama

gc_dolphin_hotkey_get

Read the current Dolphin emulator hotkey binding for a specified key, such as General/Toggle Pause, and return its binding expression or None if unbound.

Instructions

Read a Dolphin emulator hotkey binding.

key is the Hotkeys.ini key <group>/<control> (e.g. General/Toggle Pause, Save State/Save State Slot 1). Returns the current binding expression (F10, @(Shift+F1)), or None if the hotkey is unbound. This is Dolphin-only (real hardware has no emulator hotkeys).

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

Input Schema

NameRequiredDescriptionDefault
keyYes
instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does well: it discloses the return value shape (a binding expression like "F10" or "@(Shift+F1)") and the unbound case (None). It does not describe what instance_id refers to or what happens if the instance is absent, which is the main 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the purpose, then the key format, the return contract, and the scope caveat. Every sentence adds distinct information with no 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?

There is no output schema, and the description compensates by documenting the return value and the None case. For a two-parameter read tool this is nearly complete, with `instance_id` being the only unexplained element.

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 coverage is 0%, so the description must compensate. It fully specifies `key` — the `<group>/<control>` Hotkeys.ini path with two concrete examples — but 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ("Read") and resource ("Dolphin emulator hotkey binding") and scopes it to Dolphin only, which separates it from the hardware/controller siblings. The read semantics also make clear it is the counterpart of the hotkey set tool.

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?

Gives a clear usage boundary: "This is Dolphin-only (real hardware has no emulator hotkeys)" tells the agent when not to use it. It never explicitly names the write counterpart or states a prerequisite (e.g. an active emulator instance), so it stops short of full routing guidance.

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