mcp-dolphin

Overview Schema Related Servers Score Discussions

dolphin_reset

Resets the GameCube or Wii console by tapping the hardware reset button, clearing live RAM and returning the CPU to boot. Use save states to preserve game data before resetting.

Instructions

PURPOSE: Tap the GameCube/Wii hardware reset button. USAGE: Equivalent to power-cycling the reset button on the console front — game state is lost. To preserve state across the reset, dolphin_save_state first and dolphin_load_state after. BEHAVIOR: DESTRUCTIVE: clears live RAM, returns the CPU to boot. Movie state (if recording) flags the reset. RETURNS: 'Reset triggered.'

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Implementation Reference

src/tools.ts:581-581 (handler)
Tool handler - dispatches dolphin_reset call by invoking 'emulation.reset' on the bridge via DolphinClient, then returns 'Reset triggered.'
```
case "dolphin_reset":  await dol.call("emulation.reset");  return ok("Reset triggered.");
```

src/tools.ts:406-414 (schema)

Tool schema definition for dolphin_reset - name, description, and empty inputSchema (no parameters required)

{
  name: "dolphin_reset",
  description:
    "PURPOSE: Tap the GameCube/Wii hardware reset button. " +
    "USAGE: Equivalent to power-cycling the reset button on the console front — game state is lost. To preserve state across the reset, dolphin_save_state first and dolphin_load_state after. " +
    "BEHAVIOR: DESTRUCTIVE: clears live RAM, returns the CPU to boot. Movie state (if recording) flags the reset. " +
    "RETURNS: 'Reset triggered.'",
  inputSchema: { type: "object", properties: {} },
},

src/tools.ts:488-491 (registration)

Tool registration via server.setRequestHandler with ListToolsRequestSchema and CallToolRequestSchema (the switch statement routing includes dolphin_reset)

export function registerTools(server: Server, dol: DolphinClient): void {
  server.setRequestHandler(ListToolsRequestSchema, async () => ({ tools: TOOLS }));

  server.setRequestHandler(CallToolRequestSchema, async (req) => {

bridge/mcp_bridge.py:121-121 (helper)
Python bridge helper function _reset that calls Felk's emulation.reset() API
```
def _reset(_p):   emulation.reset();  return None
```
bridge/mcp_bridge.py:162-162 (helper)
Registration of 'emulation.reset' handler in the bridge's HANDLERS dispatch table
```
"emulation.reset":                _reset,
```

Tool Definition Quality

A4.9/5.0

Behavior5/5

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

No annotations are provided, so the description fully carries the burden. It explicitly declares the tool as DESTRUCTIVE, clarifies it clears live RAM and returns CPU to boot, and mentions movie state recording behavior. This is comprehensive.

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?

The description is well-structured with clear labels (PURPOSE, USAGE, BEHAVIOR, RETURNS) and is concise, containing only necessary information. It is front-loaded with the most critical information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no parameters and no output schema, the description is complete. It covers purpose, usage, behavioral impact, what it returns, and how it interacts with movie recording. No gaps remain.

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?

There are no parameters in the input schema, so the baseline is 4. The description adds no parameter-level detail, but it is not needed; however, the description itself is rich enough to satisfy the parameter semantics dimension.

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 clearly states the tool taps the GameCube/Wii hardware reset button, using the verb 'tap' and specifying the resource (reset button). It distinguishes itself from sibling tools like dolphin_save_state and dolphin_load_state by describing the destructive behavior.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use the tool ('equivalent to power-cycling the reset button') and provides alternatives: to preserve state, use dolphin_save_state first and dolphin_load_state after. This distinguishes it from other state-related siblings.

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

Install Server

Latest Blog Posts

Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
open source
OpenAI
Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dmang-dev/mcp-dolphin'

If you have feedback or need assistance with the MCP directory API, please join our Discord server