Skip to main content
Glama

gc_capture_configure

Configure an instance's capture backend by setting display, screen size, and V4L2 device, resolution, or format, then persist the change for emulator or real GameCube use.

Instructions

Configure the capture backend of an instance (e.g. display, screen_size).

For a real GameCube hardware instance, this updates the V4L2 capture device / resolution / format and persists the change. opts may include a capture dict of capture options.

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>",
      "opts": "<opts>"
    },
    "name": "gc_capture_configure"
  }
}

Input Schema

NameRequiredDescriptionDefault
optsYes
instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description does useful work: it reveals this is a mutating operation that persists, and that on real hardware it rewrites the V4L2 device/resolution/format. Gaps remain — nothing about required permissions, whether a running instance is interrupted, whether changes are reversible, or what the other instance types do.

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?

The purpose sentence is front-loaded and the hardware-specific detail follows logically, so the document reads cleanly. Minor waste from reStructuredText double-backtick markup and a slightly vague trailing sentence about the `capture` dict.

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?

This is an unannotated mutation tool with no output schema and effectively undocumented parameters, and the description leaves key agent questions open: which option keys are valid, what happens on non-hardware instances, and whether the change is reversible or takes effect immediately. For a persistence-writing configuration tool, that is not sufficient to call it confidently.

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 coverage is 0% and `opts` is an untyped free-form object with no property documentation. The description only hints that `opts` may contain a `capture` dict and lists two example keys, leaving the actual accepted option names, value formats, and instance_id semantics undocumented. It does not compensate for the coverage gap.

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?

"Configure the capture backend of an instance" states a specific verb and resource, and the parenthetical examples (display, screen_size) plus the V4L2 branch make the scope concrete. It does not explicitly contrast itself with siblings like gc_capture_backends or gc_capture_screenshot, so it stops short of a 5.

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 implied: you configure capture settings, and a special path exists for real GameCube hardware versus other instances. However, there is no explicit when-to-use/when-not guidance, no pointer to gc_capture_backends for discovering valid values, and no statement about whether this applies to emulated instances at all.

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