Skip to main content
Glama

GTA VI Easter eggs and secrets

easter_eggs
Read-only

Read GTA Wiki Easter eggs and secrets for GTA VI, filtered by topic, with sourced fallback sections when no dedicated secrets page exists.

Instructions

Read Easter eggs and secrets from the GTA Wiki. If the dedicated GTA VI secrets page does not exist, say so and return the closest sourced section, usually Trivia. Filter with topic. Unverified items are not confirmed secrets.

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

Input Schema

NameRequiredDescriptionDefault
topicNoOptional filter, for example Red Dead or Vice City.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the fallback path when the GTA VI secrets page is absent, the expectation to return the closest sourced section (usually Trivia), and the caveat that unverified items are not confirmed secrets.

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?

Four short sentences, front-loaded with the core action and followed by the fallback rule. Nothing is padded, though "Unverified items are not confirmed secrets" is phrased somewhat circularly and could be tighter.

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 one optional parameter, full schema coverage, and annotations covering the safety profile, the description supplies what remains: the fallback behavior and the reliability caveat. No output schema exists, but the description does not need to explain return values in detail given the explicit instruction about returning the closest sourced section.

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 schema already explains that topic is an optional filter with examples like Red Dead or Vice City. The description's "Filter with topic" restates this without adding syntax, matching rules, or examples, so the baseline of 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?

States a specific verb and resource: read Easter eggs and secrets from the GTA Wiki, which matches the title and is distinguishable from list_cheats or get_page. It does not name any sibling tool, so differentiation is implicit rather than explicit.

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?

"Filter with topic" gives a usage hint for the single parameter, and the fallback instruction tells the agent what to do when the dedicated page is missing. However, there is no guidance on when to prefer this tool over get_page or search_gta6, leaving the routing decision to inference.

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