Skip to main content
Glama

gc_platform_list

Lists available controllable platforms, including running Dolphin emulator instances and registered real GameCube hardware, so you can select a target.

Instructions

List the platforms currently available to control.

Includes each running Dolphin instance (dolphin:<id>) and each registered real GameCube hardware instance (gamecube-hw:<id>).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full load; it does disclose that the result reflects live currently-running instances and registered hardware, which is useful behavioral context. It does not state that the call is a safe read with no side effects, whether results are cached/ordered, or what a caller should do if a listed platform disappears before use.

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?

One short lead sentence front-loads the purpose, and the second sentence adds only the ID format detail an agent actually needs to interpret results. No filler, no restatement of the name.

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 no-parameter list tool with an output schema and no annotations, the description covers what is returned and the ID convention, which is close to sufficient. A note on how this relates to gc_instance_list/gc_hardware_list (aggregate vs. per-category detail) would close the 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 there is no parameter meaning to add beyond the schema; the baseline of 4 applies. The description instead spends its words on the shape of the values returned, which is the relevant semantic content here.

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?

States a specific verb and resource ('List the platforms currently available to control') and enumerates the two ID forms returned (dolphin:<id>, gamecube-hw:<id>), which makes the scope concrete. It never names the sibling list tools (gc_instance_list, gc_hardware_list) that return the component halves, so differentiation is inferred from the content rather than stated.

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: 'available to control' suggests calling this first to discover targets before acting. There is no explicit when/when-not guidance and no pointer to gc_instance_list or gc_hardware_list for callers who want only one category or more detail per entry.

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