Skip to main content
Glama

GTA 6 unlock time for a country

get_unlock_time
Read-onlyIdempotent

Use this when someone asks what time GTA 6 unlocks in a given country. Based on the PlayStation Store listing (local midnight on November 19, 2026). Returns the exact UTC moment, the local wall-clock label, the time-zone abbreviation and the page that explains it. The answer gives Rockstar Support’s rule, midnight local time in all regions, and what the Xbox Store catalog records.

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": {
      "country": "<country>"
    },
    "name": "get_unlock_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesCountry name, ISO code or alias, for example India, UK, US, BR

Output Schema

NameRequiredDescriptionDefault
pageNo
zoneNo
basisNo
marketNo
timeZoneNo
unlockUtcNo
localLabelNo
rockstarRuleNo
rockstarRuleUrlNo
xboxUnlockTimingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / rockstarRule
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / rockstarRuleUrl
      Added value: +{
      +  "type": "string"
      +}
    • removedOutput schema / properties / rockstarUnlockTable
      Removed value: -{
      -  "type": "string"
      -}
  2. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context beyond that: the data source (PlayStation Store listing), the underlying rule (Rockstar Support's midnight-local-time policy in all regions), and a cross-check against the Xbox Store catalog, which tells the agent how authoritative the answer is.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are well front-loaded and earn their place. The final sentence ('The answer gives Rockstar Support's rule... and what the Xbox Store catalog records') is vague about what is actually returned and partially duplicates the enumerated return fields, adding length without proportional value.

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 the description does not need to enumerate return values, yet it usefully flags the sources behind the answer. For a single-parameter lookup tool with full annotation coverage, this is nearly complete; only the ambiguous final sentence leaves the scope of the returned explanation slightly unclear.

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 description coverage is 100% and the country parameter already documents that names, ISO codes and aliases ('India, UK, US, BR') are accepted. The description adds no additional meaning about the parameter, so the baseline of 3 for high-coverage schemas applies.

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?

The description states a specific verb and resource: it returns the GTA 6 unlock time for a given country, with a concrete basis (PlayStation Store listing, local midnight November 19, 2026). It is narrow enough to be distinguishable from siblings like get_launch_countdown or get_price, though it never names those siblings explicitly.

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?

The opening sentence gives an explicit usage trigger: 'Use this when someone asks what time GTA 6 unlocks in a given country.' There are no when-not conditions and no named alternatives for adjacent questions such as countdown or price, which keeps it short of a 5.

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.