Skip to main content
Glama

gc_dolphin_freeze

Suspend a Dolphin emulator process with SIGSTOP for a hard OS-level freeze that works without X display or xdotool; use toggle pause instead for frame-advance/TAS workflows.

Instructions

Hard-freeze the Dolphin process with SIGSTOP.

This is a coarse OS-level pause that always works (no X display or xdotool needed). It is not compatible with frame-advance (the process is suspended, so it cannot process hotkeys); use gc_dolphin_toggle_pause for a TAS-friendly pause.

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

Input Schema

NameRequiredDescriptionDefault
instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/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 well: it discloses the mechanism (SIGSTOP), that the pause is coarse and OS-level, and a non-obvious side effect (suspended process cannot process hotkeys, so frame-advance breaks). It does not state that the process stays frozen until resumed (e.g. via gc_dolphin_unfreeze) or whether emulator state is preserved, which a mutation-like operation like this should mention.

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?

Two short sentences, front-loaded with the action and mechanism, followed by the compatibility caveat and the redirect. Nothing is redundant or padded.

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 one-parameter process-control tool with no output schema, the definition covers what it does, the mechanism, the risk to hotkey-driven workflows, and the better alternative. It is only slightly short of complete in not saying how the freeze is lifted or confirming that game state survives the suspension.

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?

Only one parameter, instance_id, and schema coverage is 0%, so the schema adds no meaning. The description never mentions instance_id, but a single self-descriptive identifier parameter that is required and has no enums leaves little ambiguity, so the gap is minor rather than severe.

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 ('Hard-freeze the Dolphin process') plus the mechanism (SIGSTOP), and explicitly differentiates it from the sibling gc_dolphin_toggle_pause by contrasting OS-level pause with a TAS-friendly pause. An agent can distinguish this from gc_dolphin_unfreeze or gc_dolphin_step_frame without opening any schema.

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?

Gives an explicit when-to-use ('always works, no X display or xdotool needed') and an explicit when-not ('not compatible with frame-advance ... use gc_dolphin_toggle_pause instead'), naming the alternative and the condition that selects it. This is the strongest form of routing guidance.

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