Skip to main content
Glama

GT7 collection progress

gt7_progress
Read-only

Calculate Gran Turismo 7 collection progress: see owned and missing cars plus credits needed to complete, optionally filtered by manufacturer, class, or dealership.

Instructions

How much of the Gran Turismo 7 car list is owned, how many cars are missing, and the credits needed to finish. Optionally narrowed to a manufacturer, class or dealership.

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

Input Schema

NameRequiredDescriptionDefault
makerNoManufacturer, e.g. "Porsche"
dealerNoWhere the car is sold
carClassNoGT class, e.g. "Gr.3" or "Gr.4"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/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 genuine value by disclosing the computed outputs (owned share, missing count, credit cost to finish), though it doesn't say which price source the credits figure uses or whether zero-filter calls aggregate across all cars.

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 sentences, front-loaded with the primary outputs and followed by the optional narrowing. Every clause carries information and nothing is repeated from the schema or annotations.

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?

With no output schema, the description correctly takes on the burden of naming the three returned figures, and it covers all optional filters. The one gap is the definition of the 'credits needed to finish' figure and whether the aggregates are fully unfiltered when no arguments are passed.

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%, with maker, carClass and the dealer enum all documented in the schema, so the baseline is 3. The description enumerates the same three filter axes but adds nothing about how they combine (AND vs. OR) or what happens with unmatched values.

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 computed resource: fraction of the GT7 car list owned, count of missing cars, and credits required to complete. That is clearly distinguishable from a raw lookup, but it never names its closest sibling gt7_missing_cars, so an agent must infer the split between an aggregate progress report and a missing-car list.

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 rather than stated: the phrase 'Optionally narrowed to a manufacturer, class or dealership' tells the agent filters exist but not when to apply them or when a sibling such as gt7_missing_cars would be the better call. There are no exclusions or prerequisites (e.g. whether ownership data must be populated first).

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