Skip to main content
Glama

List GTA VI things

gta6_list

List GTA VI wiki pages by topic, such as missions, vehicles, characters, weapons, or locations, with pagination to browse categories and continue results.

Instructions

List wiki pages in a GTA VI category. Topics: missions, vehicles, characters, weapons, locations, or any other topic (e.g. "radio stations", "businesses", "animals") which is matched to a GTA VI category.

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": {
      "topic": "<topic>"
    },
    "name": "gta6_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
topicYesA topic like 'vehicles' or an exact category name like 'Locations in GTA VI in Ambrosia'.
cursorNo`next` value from a previous call to continue the list.

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?

No annotations exist, so the description carries the full burden. It does disclose a non-obvious behavior: an arbitrary topic string gets matched to a GTA VI category, which tells the agent that loose topic terms are acceptable. However, it says nothing about read-only semantics, result volume, or how the cursor-based continuation behaves in practice.

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, front-loaded with the core action, and no filler. The second sentence is slightly redundant in restating that topics map to categories, but it earns its place by signaling that free-form topics are accepted.

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

Completeness3/5

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

With no annotations and no output schema, the description should say more about what a listed page looks like and how it relates to gta6_page for fetching details. Pagination is covered only by the schema's cursor field. It is adequate to call the tool but leaves the follow-up workflow implicit.

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 67%, with topic and cursor documented but limit undocumented in both places. The description's topic enumeration loosely reinforces the schema's own topic description ('vehicles', exact category names) but adds little new precision, so the baseline of 3 is appropriate.

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 gives a specific verb and resource: 'List wiki pages in a GTA VI category.' The topic enumeration (missions, vehicles, characters, weapons, locations) makes the scope concrete. It does not distinguish itself from sibling gta6_search, which likely offers overlapping coverage, so it stops short of a 5.

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 implied by the category-based framing: use this when you want an enumerated list scoped to a topic. There is no explicit statement of when to prefer gta6_search over this tool, nor any exclusion or prerequisite, leaving the agent to infer the boundary from sibling names alone.

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