Skip to main content
Glama

gc_hardware_devices

Probe Video4Linux2 capture devices on this host to find usable GameCube video nodes, listing card names, pixel formats, and capture capability so you can choose a node that can actually grab frames.

Instructions

Probe the Video4Linux2 capture devices present on this host.

A real GameCube registers one of these (e.g. /dev/video0) as its capture_device so the server can grab frames from the console. Each entry reports the node, its card name, the pixel formats it offers, and whether it can actually capture video frames (can_capture). Some nodes expose only UVC metadata and cannot produce a video stream, so prefer one with can_capture: true.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does well: it reveals that some nodes expose only UVC metadata and cannot stream, and directs the agent to can_capture. It does not spell out that this is a non-mutating probe or mention any permission or performance considerations, keeping it just short of full transparency.

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 with purpose, then context, then the caveat — easy to scan. The sentence enumerating returned fields (node, card name, pixel formats, can_capture) partially duplicates the output schema, slightly reducing the value of that line.

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 zero-parameter probe tool with an output schema, this covers what the agent needs: what it discovers, the meaning of can_capture, and the metadata-only trap. The only gap is guidance on how it relates to adjacent capture-backend 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. It correctly adds no parameter filler and instead spends its words on the result semantics.

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?

Names a specific verb (probe) and resource (Video4Linux2 capture devices on this host), and explains the domain role via the GameCube capture_device link. It is clearly distinct from controller/capture-config siblings, though it never names an alternative tool to disambiguate against gc_capture_backends or gc_hardware_list.

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: the agent gathers that this is how you discover a valid capture node and that it should prefer entries with can_capture: true. There is no explicit 'use this when...' or any statement of when another tool (e.g. gc_capture_backends) would be the better choice.

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