Skip to main content
Glama

gc_gpu_info

Reports host GPU rendering diagnostics to determine whether a GameCube instance uses a real GPU or Mesa software, and to diagnose /dev/shm SIGBUS crashes caused by insufficient shared memory.

Instructions

Report GPU rendering diagnostics for this host.

Useful for deciding whether a GameCube instance will render on a real GPU or fall back to Mesa software (llvmpipe), and for diagnosing the /dev/shm SIGBUS crash that occurs when the shared-memory filesystem is too small for Dolphin's emulated RAM.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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 discloses the diagnostic categories returned (GPU vs software fallback, shared-memory sizing) and implies a read-only report, but says nothing about response shape, cost, or whether any host access is required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences: the first states what it does, the second states why you would call it. The purpose is front-loaded and no sentence is filler, even though the second is long.

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 read tool with no output schema, the description covers what is reported and the motivating scenarios. It leaves the return structure unspecified, which is the main remaining gap.

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 the schema needs no elaboration and the baseline is 4. The description correctly spends no words on arguments and instead explains what the parameterless call yields.

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 opens with a specific verb+resource: "Report GPU rendering diagnostics for this host." That is enough to distinguish it from neighbors like gc_server_info or gc_hardware_devices, though it never names a sibling to sharpen the boundary.

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?

It gives two concrete situations that call for this tool: deciding whether an instance renders on a real GPU versus Mesa llvmpipe, and diagnosing the /dev/shm SIGBUS crash. No explicit when-not-use or named alternative is offered, so it stops short of a 5.

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