Skip to main content
Glama

gc_rom_load

Boots a game ROM on a selected Dolphin instance or real GameCube console, using host-side paths for emulators and console-side paths for hardware.

Instructions

Boot/load a ROM on an instance.

This is the unified entry point for pointing a target at a game:

  • Real GameCube hardware — sends a BOOT command to the console's Swiss netboot listener (TCP 4242 on the instance's bba_ip). rom_path must be a console-side path (sdc:/ or fsp:/, e.g. sdc:/games/Foo.iso). If the console is currently inside a game the listener is down; this first tries to return to Swiss with the A+Z+START combo (which needs hardware button pressing, not implemented yet).

    Raises :class:NetbootError if the BOOT command is not answered with OK — including when the listener returns no reply at all (console mid-boot / dropped connection) or refuses the ROM (ERR <reason>).

  • Dolphin instance — stops the current process and relaunches it booting the given host-side ROM/DOL/ELF path.

For hardware, set the console's IP with gc_hardware_update(instance_id, bba_ip='<console-ip>') before loading a ROM.

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

Input Schema

NameRequiredDescriptionDefault
rom_pathYes
instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so thoroughly: the TCP 4242 BOOT protocol, the requirement that the listener be reachable (down while inside a game), the A+Z+START recovery attempt that is not yet implemented, and the NetbootError conditions including no-reply and ERR responses. Dolphin mode's process-stop-then-relaunch behavior is also disclosed.

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 purpose sentence followed by clearly labeled bullets per target, which is well matched to the two-mode behavior. A few passages, such as the parenthetical about hardware button pressing not being implemented, are slightly verbose but still convey an operational constraint rather than filler.

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?

For a two-parameter tool with no annotations and no output schema, the description covers prerequisites, per-target path semantics, failure modes, and side effects (process restart on Dolphin). Return values are not described, but success behavior is implied by the boot/launch semantics, leaving no material gap for correct invocation.

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: rom_path is explained as a console-side path (sdc:/ or fsp:/ with an example) for hardware versus a host-side ROM/DOL/ELF path for Dolphin. instance_id's role as the target selector is only implicit through the bba_ip prerequisite, so the identifier itself remains loosely defined.

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 opening line names a specific verb and resource ('Boot/load a ROM on an instance') and the body clarifies it is the unified entry point covering two distinct targets: real GameCube hardware and a Dolphin instance. An agent can tell immediately what the tool does and that it spans both backends, which no sibling name alone conveys.

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 concrete when-to-use context for each mode: hardware requires the console's IP set via gc_hardware_update(instance_id, bba_ip=...) beforehand, and Dolphin mode restarts the current process. It does not name an alternative for save-state loading (e.g., a dolphin load-state sibling) or state explicitly when NOT to use this tool, so guidance is strong but not fully routed.

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