Skip to main content
Glama

GTA 6 launch countdown

get_launch_countdown
Read-onlyIdempotent

Use this when someone asks how long until GTA 6 launches. Returns the confirmed release date (November 19, 2026, PS5 and Xbox Series X|S), the full days left, and the exact unlock moments for New Zealand, the United Kingdom and the US East Coast. Optional: an IANA time zone such as "Asia/Kolkata" for that zone's store unlock.

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

Input Schema

NameRequiredDescriptionDefault
timezoneNoIANA time zone, for example America/Chicago or Asia/Kolkata

Output Schema

NameRequiredDescriptionDefault
noteNo
localNo
pagesNo
phaseNo
statusNo
asOfUtcNo
unlocksNo
verdictNo
releaseDateNo
rockstarRuleNo
rockstarRuleUrlNo
releaseDateLabelNo
daysUntilFirstUnlockNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / properties / local / properties / daysRemaining
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / rockstarRule
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / rockstarRuleUrl
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / unlocks / items / properties / daysRemaining
      Added value: +{
      +  "type": "number"
      +}
  2. Changed2 schema fields changed
    • addedOutput schema / properties / phase
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / verdict
      Added value: +{
      +  "type": "string"
      +}
  3. First observed

TDQS

A4/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 real context beyond that: which concrete data points come back (date, full days left, unlock moments for three named regions) and what the optional timezone changes. It says nothing about data freshness or how the static release date is validated, which would matter for a countdown.

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?

Three sentences, front-loaded with the trigger, then the payload, then the optional parameter. It is efficient overall, though enumerating New Zealand, the UK, and the US East Coast is hardcoded detail the response shape already conveys.

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?

An output schema exists, so return structure needn't be spelled out, and the single optional parameter is fully covered. For a simple read-only lookup this is close to complete; the main omission is disambiguating from get_unlock_time, which an agent would likely hesitate between.

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%, so the schema already documents the IANA string and gives examples. The description adds meaning beyond it by explaining the effect: the returned unlock is that zone's store unlock, an outcome the schema does not state. The gain is modest but real.

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: returns how long until the GTA 6 launch, plus the confirmed date, days remaining, and per-region unlock moments. An agent can identify the tool immediately. It misses an explicit contrast with the sibling get_unlock_time, whose purpose overlaps with the unlock-moment portion of this tool.

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?

'Use this when someone asks how long until GTA 6 launches' gives a clear triggering condition. It does not name an alternative or exclusion, notably get_unlock_time, which appears to cover similar unlock-time ground and should have been routed to or from explicitly.

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.