Skip to main content
Glama

GTA VI overview

gta6_overview

Retrieve official GTA 6 facts—release, platforms, PC status, setting, protagonists, timeline—and a live GTA Wiki summary.

Instructions

Official facts (release, platforms, PC status, setting, protagonists, timeline, sources) plus the live summary from the GTA Wiki.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are supplied, but the description discloses something genuinely useful: results merge 'official facts' with a 'live summary from the GTA Wiki', telling the agent the payload mixes authoritative and community-sourced data. Combined with the zero-parameter schema, this makes the read-only, no-side-effect nature self-evident. It does not mention caching, freshness, or rate limits, which keeps it below 5.

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?

A single sentence with zero filler, leading with the authoritative core ('Official facts') and closing with the secondary wiki summary. Every item in the parenthetical maps to something an agent would want to know before calling.

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?

With no output schema, the description carries the burden of describing the return payload, and the enumerated field list largely does that. What remains unknown is the concrete shape (flat keys vs. sections, prose vs. structured), which an agent cannot determine without calling — a minor but real gap for a tool with no schema documentation of its response.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and no risk of an agent mis-supplying arguments. Baseline for a parameterless tool applies; no additional credit is warranted.

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 resource (GTA VI facts) and enumerates the specific content returned: release, platforms, PC status, setting, protagonists, timeline, sources, plus the wiki summary. That is concrete enough that an agent can tell this is the 'everything at a glance' tool rather than a list, page, or search tool. It falls short of 5 because it never explicitly contrasts itself with the sibling lookup tools.

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 this is the entry point for broad 'what do we know about GTA VI' questions and that lookup-specific siblings exist. There is no explicit when-to-use or when-not-to-use statement, and no sibling is named as an alternative.

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