Skip to main content
Glama

gc_platform_capabilities

Describe the capabilities of a specified platform, such as a Dolphin emulator instance or GameCube hardware, so you can identify its supported features before running commands.

Instructions

Describe the capabilities of a platform.

platform may be dolphin:<instance_id> or gamecube-hw:<id>.

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": {
      "platform": "<platform>"
    },
    "name": "gc_platform_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformYes

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 supplied, the description must carry the behavioral burden. "Describe" implies a non-mutating read, and the accepted identifier forms are disclosed, but nothing is said about error behavior, whether the platform must be running/connected, or what kind of capability data comes back.

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 short sentences, front-loaded with the purpose and followed by the only piece of format information an agent needs. No filler.

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?

For a single-parameter read tool this is close to sufficient, but there is no output schema, and for a tool whose entire value is the returned capability description, the description says nothing about what that content looks like or how large it is.

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?

Schema description coverage is 0% and the single `platform` parameter has no schema-level documentation, so the description's specification of the two accepted forms (`dolphin:<instance_id>` and `gamecube-hw:<id>`) is doing real work. It stops short of explaining where instance_id/id values come from, which is a residual 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?

States a specific verb and resource: "Describe the capabilities of a platform." An agent can tell this is an introspection/query tool, but the description never contrasts it with the sibling gc_platform_list, which an agent might reasonably confuse it with.

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 versus gc_platform_list or gc_gpu_info, no stated prerequisites, and no note about what happens with an unknown or unreachable platform. Usage is only inferable from the name.

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