Skip to main content
Glama

Search GTA VI

search_gta6
Read-only

Search the GTA Wiki and Wikipedia for Grand Theft Auto VI pages, characters, locations, or release facts and get ranked results with snippets, source URLs, and CC BY-SA attribution.

Instructions

Search the GTA Wiki for a Grand Theft Auto VI page. Release, sales, and platform questions also search Wikipedia. Returns ranked hits with snippets, source URLs, and CC BY-SA attribution.

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": {
      "query": "<query>"
    },
    "name": "search_gta6"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWhat to look up, for example Lucia Caminos or Leonida.

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 cover read-only and open-world behavior, and the description adds real substance: dual-source search (GTA Wiki plus Wikipedia for certain topics), ranked results, snippets, source URLs, and CC BY-SA attribution. It does not state result counts, pagination, or what happens on zero hits, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core action, with no filler. The second sentence's phrasing ("Release, sales, and platform questions also search Wikipedia") is slightly compressed but still parseable.

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 single-parameter search tool with no output schema, the description compensates by describing the return payload (ranked hits, snippets, source URLs, attribution). Missing only edge-case behavior such as empty results or result limits.

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?

With one parameter at 100% schema coverage, the schema already defines the query and supplies examples like "Lucia Caminos or Leonida." The description adds only that certain topic areas trigger a Wikipedia search, which is routing behavior rather than query syntax guidance.

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?

"Search the GTA Wiki for a Grand Theft Auto VI page" gives a specific verb and resource and implicitly separates itself from get_page (search vs. fetch a known page). It stops short of naming siblings explicitly, so the distinction is inferable rather than stated.

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?

It signals the kind of questions it suits (release, sales, platform) and that such queries also fan out to Wikipedia, which implies usage for Q&A-style lookups. It never says when to prefer get_page or the sibling tools instead, leaving the agent to infer that.

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