GTA6 Times

Tracked GTA 6 markets and price status

list_markets

Read-onlyIdempotent

Use this when someone asks which countries GTA 6 prices are tracked for, or which prices are confirmed. Lists every tracked market (101 today) with the price status of each; prices were last fully rechecked on November 4, 2026. Optional filter by status.

Input Schema

Name	Required	Description	Default
`status`	No	Only markets with this price status: confirmed (read from the local store), reported (a named outlet reported it), estimate (not yet confirmed), usd (the store bills in US dollars), unlisted (the local store exists and does not list GTA 6), none (no local store). Leave out for every market.

Output Schema

Name	Required	Description	Default
`page`	No
`count`	No
`markets`	No
`pricesVerified`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 4, 2026

changedInput schema / properties / status / description

Previous value: -"Only markets with this price status: confirmed (read from the local store), reported (a named outlet reported it), estimate (not yet confirmed), usd (the store bills in US dollars), none (no local store). Leave out for every market."New value: +"Only markets with this price status: confirmed (read from the local store), reported (a named outlet reported it), estimate (not yet confirmed), usd (the store bills in US dollars), unlisted (the local store exists and does not list GTA 6), none (no local store). Leave out for every market."

changedInput schema / properties / status / enum

Previous value: -[
-  "confirmed",
-  "reported",
-  "estimate",
-  "usd",
-  "none"
-]New value: +[
+  "confirmed",
+  "reported",
+  "estimate",
+  "usd",
+  "unlisted",
+  "none"
+]

Changed1 schema field changedOct 27, 2026

addedInput schema / properties / status / description

Added value: +"Only markets with this price status: confirmed (read from the local store), reported (a named outlet reported it), estimate (not yet confirmed), usd (the store bills in US dollars), none (no local store). Leave out for every market."

First observedOct 26, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive/non-open-world, so the safety profile is covered. The description adds value the annotations cannot: the market count (101), a data-freshness anchor ('last fully rechecked on November 4, 2026'), and the fact that filtering is optional and returns everything by default. It doesn't discuss ordering or result size, but with 101 records that is a minor gap.

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, front-loaded with the usage trigger before the behavioral description. Every clause carries information: trigger, scope, count, status dimension, freshness date, and default filtering behavior. No filler.

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 values needn't be explained, and the single optional enum param is fully described in the schema. The description supplies the freshness and scale context needed to interpret results. The only missing piece is an explicit pointer to the single-market sibling for the 'one country' case.

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 enum values are individually explained in the schema (confirmed, reported, estimate, usd, unlisted, none). The description only says 'Optional filter by status' and adds no semantics beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource: 'Lists every tracked market ... with the price status of each'. This is clearly separable from siblings like get_price (a single price) and check_claim, and it adds concrete scope (101 markets) rather than restating the title.

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 which countries GTA 6 prices are tracked for, or which prices are confirmed' gives explicit triggering questions, which is exactly the routing information an agent needs. It stops short of naming the alternative tool (get_price) for a single-country lookup, so the boundary is implied rather than stated.

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

All GTA6 Times tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.