Skip to main content
Glama

gc_instance_status

Retrieves detailed status for a specified GameCube instance, helping you monitor emulator or hardware state by instance ID.

Instructions

Get detailed status for one 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_instance_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?

No annotations are supplied, so the description carries the full burden of disclosure. Beyond the implication that "Get" is a read operation, it says nothing about what fields "detailed status" includes, whether it fails for a stopped or nonexistent instance, or what the caller receives back.

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 short sentence with the resource and scope front-loaded and no filler. It is efficient, though the brevity is close to under-specification rather than genuine concision.

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?

The tool is simple (one required parameter, no nested objects), but with no annotations and no output schema, the description should explain at least the rough shape of the returned status or the failure modes. It leaves the agent guessing about both.

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% for the single instance_id parameter, so the description is the only source of meaning. It conveys merely that the tool operates on exactly one instance, adding no information on identifier format, source of valid IDs, or behavior for unknown values.

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 pairs the specific verb "Get" with the resource "detailed status for one instance," which is enough to distinguish it from list-style siblings like gc_instance_list. It stops short of explicitly naming what distinguishes it from gc_hardware_status, but the singular-instance scope is clear.

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 call this instead of gc_instance_list or gc_hardware_status, and no stated preconditions such as the instance needing to exist or be running. The agent must infer the selection context entirely from the tool name.

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