Skip to main content
Glama

Missing GT7 cars

gt7_missing_cars
Read-only

List cars not yet in your Gran Turismo 7 garage with price and where to buy them; filter by maker, class, dealer, or max price and sort to plan purchases.

Instructions

List cars not yet in the garage, with price and where to buy them. Sort cheapest-first to plan the next purchase, or priciest-first to see what dominates the cost. maxPrice limits it to what is affordable.

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

Input Schema

NameRequiredDescriptionDefault
sortNocheapest
limitNo
makerNoManufacturer, e.g. "Porsche"
dealerNoWhere the car is sold
carClassNoGT class, e.g. "Gr.3" or "Gr.4"
maxPriceNoOnly cars costing at most this many credits

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that results are restricted to unowned cars and include price and dealer, but says nothing about how limit truncation behaves or what the result shape looks like.

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?

Two compact sentences, front-loaded with the scope, then the sort rationale and the price cap. No filler and nothing repeated from the schema verbatim.

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 six-parameter, read-only listing tool with no output schema, the description covers what it returns, its ownership scoping, sort semantics and the price filter. Only the limit/truncation behavior of the result set is left implicit.

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 67% and the description fills the biggest gap: the 'sort' enum has no schema description, and the text explains what cheapest-first versus priciest-first are for. It also reinforces maxPrice as an affordability cap. The limit parameter's truncation behavior remains unaddressed in both places.

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?

Names a specific verb and a tightly scoped resource: 'List cars not yet in the garage' — the garage filter is what separates this from a general car lookup. It also states what comes back (price, where to buy). It does not name the sibling to use instead, so it stops short of 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?

Gives practical usage framing for two sort modes ('plan the next purchase' vs 'see what dominates the cost') and says maxPrice narrows to affordable cars, but these are parameter-use hints rather than tool-selection guidance. No when-not condition and no explicit alternative such as gt7_find_car for cars already owned.

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