Skip to main content
Glama

gc_hardware_list

Lists all registered real GameCube hardware instances so you can identify available devices before launching ROMs or manipulating controller ports.

Instructions

List all registered real GameCube hardware instances.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gc_hardware_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; it implies a non-mutating enumeration via "List all" and signals that no filtering is applied. It does not state whether results include disconnected devices, whether the list can be empty, or ordering, which an agent would want before calling. Since an output schema exists, omitting return-value details is acceptable.

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. It is efficient, though the qualifier "real" is never defined, leaving a mildly ambiguous word in an otherwise tight statement.

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

Completeness3/5

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

For a zero-parameter list tool with an output schema, the description covers the essentials and need not describe return values. The remaining gap is the undefined distinction between "real" and emulated hardware and how it relates to the neighboring hardware tools.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless schema applies. "all registered real" correctly conveys that no filter arguments exist.

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 ("List") and resource ("registered real GameCube hardware instances"), so the agent knows this is a read of hardware registrations. It is not explicitly differentiated from the sibling gc_hardware_devices, so the boundary between the two is left to inference.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can reasonably infer this is the call to enumerate registered hardware, and no parameters means no prerequisites to explain. There is no explicit when-to-use versus gc_hardware_devices or gc_hardware_status, and no exclusion of unregistered/emulated devices beyond the word "registered".

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