Skip to main content
Glama

Tipline: unofficial GTA 6 guide

GTA 6 release time by country

gta6_release_times
Read-onlyIdempotent

When Grand Theft Auto VI unlocks in each country (UTC and local time), the rules behind it, and sources.

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_release_times"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoOptional country name or ISO code to filter, e.g. 'Brazil' or 'AE'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered. The description adds value by disclosing what content comes back (UTC and local times, the rules behind them, and sources) even though there is no output schema. It stops short of describing format, coverage gaps, or how the country filter changes the response shape.

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?

One compact sentence fragment with zero filler, front-loading the subject (unlock times by country) ahead of supporting detail (rules, sources). The terseness borders on under-specification rather than verbosity, but nothing is wasted.

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?

For a read-only lookup with a single well-documented optional parameter and no output schema, the description covers what the tool answers and what the response contains. The only meaningful omission is routing guidance relative to the sibling tools.

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 single country parameter is documented with concrete examples ('Brazil', 'AE'). The description never mentions the filter at all, so it adds no meaning beyond the schema; baseline 3 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 names the specific resource and dimension: unlock times for GTA VI per country, in both UTC and local time, plus the underlying rules and sources. That is clearly distinct from the sibling names (entry/listing/search), though it does not explicitly say how it differs from them.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer you call this when you need country-specific unlock times. There is no explicit when-to-use or when-not statement, and no pointer to get_gta6_entry, list_gta6_entries, or search_gta6_guide as alternatives.

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