Skip to main content
Glama

Read a GTA VI wiki page

get_page
Read-only

Fetch a short plain-text summary of a GTA Wiki page or section, with source URL and CC BY-SA attribution, falling back to Wikipedia for release, sales, or platform facts.

Instructions

Fetch a short plain-text summary of one GTA Wiki page, or one section. Uses Wikipedia when the page is missing or the section is a release, sales, or platform fact. Always includes the source URL and CC BY-SA attribution. Returns found:false instead of inventing a page.

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

Input Schema

NameRequiredDescriptionDefault
titleYesWiki page title, for example State of Leonida or Grand Theft Auto VI.
sectionNoOptional heading, for example Story or Online.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries the real behavioral load and does so well: it discloses the fallback to Wikipedia for missing pages and release/sales/platform facts, the always-included source URL and CC BY-SA attribution, and the found:false no-hallucination contract. It leaves out whether the summary is cached, truncated, or rate-limited, which keeps it off 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?

Three short sentences, zero waste, with the core action front-loaded and the fallback, attribution, and failure-mode facts following in descending priority. Every clause carries distinct information an agent would otherwise have to guess.

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 correctly compensates by naming the return format (short plain text), the accompanying source URL and attribution, and the found:false sentinel for misses. For a two-parameter read tool this covers nearly everything an agent needs, with only summary length or section-mismatch behavior left unstated.

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 coverage is 100%, so both parameters are already documented in the schema and the baseline is 3. The description adds modest meaning by framing 'section' as narrowing to one heading of a page, but gives no syntax, casing, or fallback behavior specific to an invalid section value.

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 opens with a specific verb and resource: 'Fetch a short plain-text summary of one GTA Wiki page, or one section,' which tells an agent exactly what comes back and at what granularity. It does not name a sibling or state explicitly that it differs from search_gta6, so it stops short of full sibling differentiation.

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: the required 'title' parameter suggests this is the tool for when you already know the page name, and the Wikipedia fallback describes source routing rather than when-to-use guidance. There is no explicit statement of when to prefer this over search_gta6 or what to do when no exact title is known.

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