Skip to main content
Glama

gc_instance_list

Lists all known Dolphin emulator and registered GameCube hardware instances along with their current status.

Instructions

List all known instances and their status.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full load: it discloses that the result is unfiltered ("all known instances") and includes status, which is meaningful behavioral context. It does not say whether "known" means currently running instances, registered-but-stopped instances, or a remote registry, nor whether the call is a live probe with latency or side effects.

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?

A single front-loaded sentence with no filler; every word (list, all, known, status) contributes to the agent's understanding of scope and payload.

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?

A simple zero-parameter read tool with an output schema is mostly self-explanatory, and the description needn't explain return values. However, the ambiguity of "known" instances versus running instances is exactly the question an agent needs answered when choosing between this and gc_instance_status, and it is left unresolved.

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 description has nothing to disambiguate and the baseline of 4 applies. No parameter meaning is lost or misrepresented.

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 gives a specific verb and resource ("List all known instances") and adds the payload detail "and their status," which indirectly distinguishes it from the single-instance gc_instance_status. It stops short of naming or explicitly contrasting the sibling, so an agent must infer the difference from the plural/"all" phrasing alone.

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 when-to-use or when-not-to-use guidance, and no alternative is named. The context is implied by the verb (enumeration/discovery), but an agent comparing this against gc_instance_status or gc_instance_start gets no routing signal from the definition.

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