Skip to main content
Glama

Sixfigs

Search game facts

search_guides
Read-onlyIdempotent

Returns sourced facts about Grand Theft Auto VI from the Sixfigs dataset that match a query: player warnings, cheats, map locations, money methods, vehicles and release status. Use this when the user asks a factual question about the game that the other Sixfigs tools do not cover, such as cheats, missable content, save rules or where a place is. Covers Grand Theft Auto VI only; returns no result rather than a guess when nothing matches. Facts are compiled from named sources after the game's 19 Nov 2026 release; each result shows its status (official, confirmed, single-source or disputed), sources and verified date. Pass max_chapter to include content up to the player's chapter.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results (default 5).
queryYesSearch terms, e.g. "cash limit" or "cheats trophies".
max_chapterNoStory chapter the player has reached. Content from later chapters is left out. Without it, major story spoilers are left out.

Output Schema

NameRequiredDescriptionDefault
urlYes
noteNo
queryYes
resultsYes
verifiedOnYes
spoilerNoteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses meaningful behavior: it returns no result rather than guessing, facts come from named sources after the 19 Nov 2026 release, and each result carries a status, sources, and verified date. It also explains the spoiler behavior of max_chapter, which is important for how results are shaped.

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?

The description is front-loaded with the core purpose and then supplies only relevant usage, scope, provenance, and spoiler details. It is dense and mostly earns its length, though it could be structured more scannably for such a feature-rich paragraph.

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?

Given the annotations, an output schema, and three parameters, the description covers what the tool returns, when to use it, scope limits, no-result behavior, provenance/status metadata, and spoiler handling. An agent has enough context to call it correctly without relying on undocumented assumptions.

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 the schema already explains query, limit, and max_chapter, including defaults and chapter-based filtering. The description reinforces max_chapter as the player's chapter and notes spoiler omission, but it adds little parameter meaning beyond what the schema already states.

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?

The description states a specific verb and resource: returns sourced Grand Theft Auto VI facts from the Sixfigs dataset matching a query, and lists the covered fact types. It also distinguishes itself from the other Sixfigs tools by saying to use it for factual questions those tools do not cover.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear usage condition: when the user asks a factual question about the game that other Sixfigs tools do not cover, with examples such as cheats, missable content, save rules, and locations. It also states the scope limit of Grand Theft Auto VI only, but it does not name the specific sibling tools or give explicit cases where it should not be used.

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