Skip to main content
Glama

Tipline: unofficial GTA 6 guide

Search the GTA 6 guide

search_gta6_guide
Read-onlyIdempotent

Search Tipline's sourced notes about Grand Theft Auto VI (characters, places, vehicles, weapons, activities, systems, release info; missions, cheats and collectibles as they are confirmed after launch). Returns short entries, each with its page URL and original sources. Only sourced facts; if nothing matches, the guide doesn't know yet.

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_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOptional entry type filter
limitNoHow many entries to return (1 to 10)
queryYesWhat to look for, in English, e.g. 'Ultimate Edition cars' or 'who is Cal'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"How many entries to return (1 to 10)"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds real behavioral value beyond that: it discloses the return shape ('short entries, each with its page URL and original sources'), the sourcing discipline ('Only sourced facts'), and crucially the empty-result semantics, telling the agent that a miss means the guide lacks the fact rather than that the query failed. It does not discuss ranking or relevance ordering.

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?

Two sentences, with the resource and the return shape front-loaded and the caveat about unsourced facts placed last where it belongs. The long parenthetical enumerations are dense but they are the substance of the tool's scope, not filler. Slightly heavy on list-of-nouns for a definition this short.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden of describing returns, and it does: short entries, page URL, original sources, plus what an empty result means. Combined with annotations that settle the safety profile and a fully documented schema, an agent has everything needed to call this correctly and interpret the response.

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%, so query, type and limit are all documented in the schema, including the enum members and the 1-10 limit bounds. The description's parenthetical domain list loosely mirrors the enum but adds no format, syntax or defaulting detail beyond what the schema already states. Baseline 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?

The description names a specific verb ('Search') and resource ('Tipline's sourced notes about Grand Theft Auto VI') and enumerates the covered domains (characters, places, vehicles, weapons, activities, systems, missions, cheats, collectibles). An agent knows exactly what corpus is being queried. It stops short of 5 because it never contrasts itself with the sibling retrieval tools (get_gta6_entry, list_gta6_entries), leaving the search-vs-fetch distinction to be inferred.

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 by the word 'Search' and the example queries in the schema. There is no explicit when-to-use statement, no guidance on when to prefer list_gta6_entries or get_gta6_entry over searching, and no note about how broad or narrow a query should be. The 'if nothing matches, the guide doesn't know yet' line is about interpreting results, not about selecting the tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources