Skip to main content
Glama

gc_hardware_update

Update a registered GameCube hardware instance's settings and persist them, including BBA IP, capture device, ports, and info annotation, so ROM loading can reach the netboot listener.

Instructions

Update a registered hardware instance's settings and persist them.

Use this to set the console's bba_ip (its own IP) so gc_rom_load can reach the Swiss netboot listener, or to change the capture device / ports / info annotation.

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_hardware_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
infoNo
bba_ipNo
captureNo
bba_portNo
instance_idYes
capture_deviceNo
serial_devicesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose that changes are persisted and hints at a cross-tool dependency, but it never explains the critical partial-update semantics: all six optional fields default to null, and an agent cannot tell whether omitting a field leaves it unchanged or whether passing null clears it. Permissions, error behavior, and reversibility are also unaddressed.

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?

Two short sentences, front-loaded with the core action before the use cases. The RST double-backtick markup adds mild visual noise but no real waste; every sentence carries information.

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

Completeness2/5

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

For a seven-parameter mutation tool with no annotations and no output schema, the description should do much more. The absence of any statement about partial-update semantics, null defaults, or what the persisted result looks like leaves an agent guessing on the most consequential aspect of calling it.

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 description coverage is 0%, so the description must compensate for seven undocumented parameters. It covers five of them (bba_ip, bba_port, capture, capture_device, info) and adds genuine meaning for bba_ip ('its own IP' consumed by gc_rom_load), but leaves serial_devices and instance_id unexplained and gives no formats, defaults, or null-handling for any field.

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: 'Update a registered hardware instance's settings and persist them.' The word 'registered' plus 'update' separates it from gc_hardware_register and gc_hardware_remove, and the second sentence names the fields it touches. It does not explicitly contrast itself with any sibling beyond naming gc_rom_load as a downstream consumer.

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 concrete, actionable when-to-use case: setting bba_ip so gc_rom_load can reach the Swiss netboot listener, plus the alternate case of changing capture device, ports, or the info annotation. No when-not guidance or preconditions (e.g., instance must already exist) are stated, which keeps it below a 5.

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