Skip to main content
Glama

Search the GTA Wiki

gta6_search

Search the GTA Wiki for Grand Theft Auto VI facts, prioritizing GTA VI pages and returning cited URLs plus a GTA VI flag for each hit.

Instructions

Full-text search of the GTA Wiki, prioritising GTA VI pages (each hit has gta6=true/false and a URL).

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the important prioritisation behavior and that each hit includes gta6=true/false and a URL, but it omits limits, ranking details, and pagination/error behavior.

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?

The definition is a single front-loaded sentence with no wasted words. The prioritisation detail and result-field note are both useful and compact.

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 low-complexity search tool with no output schema, the description gives the essential return context (gta6 flag and URL) and a key behavioral trait (GTA VI prioritisation). The main gap is limit behavior, though the schema supplies the default and maximum.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for two parameters. The description implies that a search query is required, but it does not explain the query parameter or the limit parameter's role or constraints beyond what the schema already shows.

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 verb and resource: full-text search of the GTA Wiki. It also names a distinguishing scope (prioritising GTA VI pages), although it does not explicitly contrast with siblings like gta6_page.

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?

Search usage is strongly implied by 'full-text search', and the prioritisation note gives context for GTA VI queries. However, there is no explicit guidance on when to use this versus gta6_page or gta6_list.

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