Skip to main content
Glama

Sixfigs

Find vehicles

find_vehicles
Read-onlyIdempotent

Returns Grand Theft Auto VI vehicles from the Sixfigs dataset that match a name or class: how and where to get each one, unlock chapter, edition requirements, and price, seats and top speed where sources state them, with status and sources. Use this when the user asks about a specific vehicle or a type of vehicle in the game. Fields no source states are left empty rather than estimated. Pass max_chapter to leave out vehicles from later chapters.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_vehicles"
  }
}

Input Schema

NameRequiredDescriptionDefault
classNoVehicle class, e.g. "sports" or "boat".
limitNoMaximum vehicles (default 5).
queryNoVehicle name or part of it.
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
vehiclesYes
verifiedOnYes
spoilerNoteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds genuinely new behavior: unstated fields are left empty rather than estimated (data-quality policy) and later-chapter content is suppressed by default to avoid story spoilers. It stops short of describing pagination/limit interaction or return envelope details.

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?

Front-loaded with the return payload, then the usage trigger, then field-fidelity and spoiler notes — a sensible order. The middle sentence is dense but every clause carries information; slight redundancy between the 'match a name or class' opener and the usage sentence keeps it from a 5.

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?

For a read-only, four-optional-parameter lookup tool with a full output schema, the description covers what is returned, when to call it, how missing data is represented, and the spoiler-safety default. Nothing an agent needs to invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description goes beyond it by explaining the default spoiler-suppression semantics of max_chapter ('content from later chapters is left out', and omitting it excludes major spoilers) and by tying query and class to name/type matching. Limit behavior is not elaborated in prose, but the schema covers it.

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?

States a specific verb and resource ('Returns Grand Theft Auto VI vehicles from the Sixfigs dataset') and enumerates the payload: how/where to get each one, unlock chapter, edition requirements, price, seats, top speed, status and sources. That is far more specific than the sibling tools (money methods, guides, status) and lets an agent route correctly without opening the schema.

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?

'Use this when the user asks about a specific vehicle or a type of vehicle in the game' gives a clear positive trigger, and the max_chapter sentence gives a conditional usage rule for spoiler-sensitive queries. No explicit 'do not use' or named alternative is given, but the sibling set is functionally distinct enough that this is only a minor gap.

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