Skip to main content
Glama

Platform & controller info

gta6_platform

Check GTA VI PC/Mac availability and get console-specific PlayStation or Xbox button names, so players know what their platform supports.

Instructions

What the player's computer can/can't do for GTA VI (no PC/Mac version yet), PC release status, and controller button vocabulary for their console.

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": "gta6_platform"
  }
}

Input Schema

NameRequiredDescriptionDefault
consoleNoPlayer's console, if known.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.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 disclosure burden, yet it says nothing about whether this is a static knowledge lookup, whether the response varies by console, or how authoritative/current the PC release status is. It does at least frame the subject matter as reference information about the player's machine and console.

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 compact sentence with no filler, and the primary subject (platform capability for GTA VI) is front-loaded. The parenthetical aside about no PC/Mac version slightly interrupts the flow of the content list.

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 small informational tool with one optional enum parameter, no annotations, and no output schema, the description conveys the topic areas but not what a response looks like or what happens when console is omitted. It is minimally adequate but leaves real gaps about return shape and optional-parameter behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single optional 'console' parameter is fully documented in the schema, so the baseline is 3. The phrase 'controller button vocabulary for their console' adds a little meaning by implying the console enum selects which button names are returned, but no further format detail is given.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun phrase listing three content areas (platform capability, PC release status, controller button vocabulary) rather than a verb plus resource, so it's unclear whether the tool looks up, generates, or answers. The content is specific enough that an agent can tell it isn't gta6_list or gta6_search, but the actual operation is left implicit.

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 guidance, no prerequisites, and no mention of the sibling tools (gta6_list, gta6_overview, gta6_page, gta6_search) that an agent might otherwise pick. The parenthetical '(no PC/Mac version yet)' is content, not routing guidance.

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