Skip to main content
Glama

Read a GTA Wiki page

gta6_page

Read GTA VI wiki pages with spoiler-safe filtering, preferring GTA VI articles; fetch infoboxes, sections, categories, plain text, or a specific section.

Instructions

Read a page (automatically prefers the GTA VI version, e.g. 'Lucia' → the GTA VI article). Returns infobox, sections, categories, spoilerRisk and plain text; story-heavy text is withheld unless spoilers=true. Use section to read one section (e.g. 'Walkthrough', 'Locations', 'Trivia').

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>"
    },
    "name": "gta6_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
sectionNo
maxCharsNo
spoilersNoOnly set true after the player agreed to story spoilers. When false, spoiler-heavy pages/sections are withheld and safe sections are suggested.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden well: it names the exact return payload (infobox, sections, categories, spoilerRisk, plain text), explains the title-resolution behavior, and states that story-heavy content is withheld unless spoilers=true. It does not cover failure modes for missing pages or truncation behavior at maxChars, which keeps it below a 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?

Two sentences, both densely informative, with the key resolution behavior front-loaded and the return contents enumerated compactly. No filler or restatement of the tool name.

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 4-parameter read tool with no output schema, the description does the necessary work: it enumerates return fields and explains the spoiler-gating policy so the agent can sequence consent. It falls short only on `maxChars` semantics and on what happens when a page or section is not found.

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?

Schema coverage is only 25%, so the description must compensate, and it does for two of four parameters: it explains that `title` is resolved against the GTA VI variant and gives concrete examples of valid `section` values ('Walkthrough', 'Locations', 'Trivia'). `maxChars` is left entirely undocumented in both schema and description, which is the remaining gap.

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 ('Read a page') and adds the distinguishing behavior that it auto-prefers the GTA VI version of a title, with a concrete example ('Lucia' → GTA VI article). An agent knows exactly what this returns versus a generic fetch.

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?

Gives partial guidance: 'Use `section` to read one section' steers toward targeted reads, and the spoiler rule implies a precondition. However, it never states when to choose this over a search or overview-style sibling, and no exclusions are named.

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