Skip to main content
Glama

gc_hardware_status

Retrieve detailed status for a specified GameCube hardware instance using its instance ID, including emulated Dolphin instances and registered real hardware.

Instructions

Get detailed status for one hardware instance.

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

Input Schema

NameRequiredDescriptionDefault
instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure and mostly fails it. 'Get' implies a read-only operation, but the description never states what 'detailed status' actually contains, how errors for an invalid instance_id are surfaced, or any permission requirements.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the terseness comes at the cost of the specification gaps noted elsewhere.

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 tool with no annotations and no output schema, the description should describe what the returned status includes and how to obtain a valid instance_id. Neither is present, so the agent cannot tell what it will receive or how to call it correctly on the first attempt.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 define instance_id and it does not — no format, no source (e.g., whether it comes from gc_hardware_list), no distinction between a hardware instance id and an emulator instance id. The phrase 'one hardware instance' adds only slight meaning beyond the field name.

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?

The description states a specific verb and resource: 'Get detailed status for one hardware instance' clearly identifies a single-object read operation. However, it offers no differentiation from nearby siblings such as gc_instance_status or gc_hardware_devices, leaving the agent to guess which status tool applies.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus gc_instance_status, gc_hardware_devices, or gc_hardware_list, and no stated preconditions. The only implicit cue is the singular 'one hardware instance' versus presumably list-oriented siblings.

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