Skip to main content
Glama

Missing GT7 cars in a dealership today

gt7_in_stock_today
Read-only

Lists Gran Turismo 7 cars missing from your garage that are in today's Used or Legend Cars stock, ordered by soonest departure so you can decide whether to buy now.

Instructions

Missing cars that are in today's Used Cars or Legend Cars stock, soonest to leave first. These rotate daily and may not come back for months, so this is the "buy now or wait" list.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral context absent from annotations: the stock rotates daily, items may not reappear for months, and results are sorted by urgency. It stops short of describing return shape, but no output schema exists and the list semantics are clear enough.

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, no filler. The scoping ('missing cars in today's stock') comes first, followed by the ordering and the volatility rationale that motivates acting on the result.

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 zero-parameter, read-only list tool with no output schema and full annotation coverage, the description covers what is returned, how it is ordered, and why it matters. The one gap is that it does not mention the dependence on ownership data being recorded (the gt7_set_owned sibling), which an agent might need to know if results look empty.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly signals that the call needs no arguments by describing a fixed, date-scoped query.

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 states a specific resource and scope: the subset of cars the user is missing that happen to be in today's Used Cars or Legend Cars stock, ordered by departure date. It is clear what the tool returns, but it does not explicitly contrast itself with the sibling gt7_missing_cars, so an agent must infer the difference from the 'today's stock' qualifier.

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?

The 'buy now or wait' framing implies the decision context in which this list matters, and 'soonest to leave first' hints at urgency triage. However, there is no explicit statement of when to call this versus gt7_missing_cars or gt7_find_car, and no prerequisites or exclusions are given.

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