Skip to main content
Glama

List GTA VI cheats

list_cheats
Read-only

Retrieve GTA VI cheat codes with code, effect, unlock, platform, source URL, and confidence rating; filter by PS5, Xbox, or PC and avoid unverified codes.

Instructions

Parse Cheats in GTA VI into rows of code, effect, unlock, platform, source URL, and confidence. confidence is confirmed only when the wiki cites a reliable source or two independent sources agree. Never present an unverified code as real. platform may be ps5, xbox, or pc.

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

Input Schema

NameRequiredDescriptionDefault
platformNoOptional: ps5, xbox, or pc.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful behavior: the confidence rule (confirmed only with a cited reliable source or two independent sources) and the mandate not to present unverified codes as real. It does not describe return format, pagination, or what happens when no cheats match.

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?

Front-loaded with the parsing action and output columns, followed by the confidence rule and platform values. Slightly redundant in repeating the platform enum already present in the schema, but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single optional-parameter read tool with annotations covering safety and no output schema, the description covers aggregation behavior and the confidence policy. However, with no output schema, it should say more about the returned structure or how empty results behave, so it is adequate but not complete.

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 parameter already documents 'Optional: ps5, xbox, or pc'. The description restates the same allowed values ('platform may be ps5, xbox, or pc') without adding filtering semantics such as whether omitting it returns all platforms. Baseline 3 applies since the schema carries the parameter meaning.

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 action (parse cheats) on a specific resource (GTA VI cheats) and enumerates the output row fields. It does not name or differentiate itself from the siblings easter_eggs, get_page, or search_gta6, so it stops short of a 5.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus the sibling tools, nor any prerequisites or exclusions. The only directive is a data-integrity rule ('Never present an unverified code as real'), which is about output quality rather than tool selection.

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

Deploy Server

Other Tools