Skip to main content
Glama

Sixfigs

Check release, platform and patch status

check_status
Read-onlyIdempotent

Returns the release date, platforms, PC version status, online mode status and latest official patch of Grand Theft Auto VI, each with its source and verified date. Use this when the user asks whether the game is out, which platforms it is on, whether a PC version or online mode exists, or which patch is current. PC and online answers report announcement status only.

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

Input Schema

NameRequiredDescriptionDefault
topicNoWhich status to return (default all).

Output Schema

NameRequiredDescriptionDefault
urlYes
noteNo
itemsYes
verifiedOnYes
latestPatchYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine behavioral context beyond that: every returned item carries a source and verified date, and PC/online entries report announcement status only rather than confirmed availability. It does not discuss caching or rate limits, but none are plausibly needed for a static reference lookup.

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 sentences, zero filler. The payload description comes first, usage triggers second, and the PC/online caveat closes it exactly where it matters. Every clause carries information an agent would otherwise have to guess.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one optional enum parameter), an output schema already defines the return shape, and annotations cover safety. Given that, the description supplies everything an agent still needs: what topics exist, when to reach for it, and the announcement-status caveat on two of the answers.

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 coverage is 100% and the sole enum parameter is fully documented with a stated default, so the baseline is 3. The description earns an extra point by qualifying what two enum values actually mean in practice — that pc and online results are announcement-status only, not confirmed existence — which changes how an agent should interpret those responses.

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

Purpose5/5

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

The description names a specific verb ("Returns") and enumerates the exact resource set: release date, platforms, PC version status, online mode status, and latest official patch for GTA VI. That is a concrete scope an agent can distinguish from siblings like find_vehicles or get_money_methods without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit use triggers matching real user phrasings ("whether the game is out," "which platforms it is on," "which patch is current"). It does not name any alternative tool or state when not to use it, but the sibling domains are clearly disjoint, so the guidance is clear if not exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources