Skip to main content
Glama

Find a GT7 car

gt7_find_car
Read-only

Look up Gran Turismo 7 cars by name or maker to check ownership, price, and dealership availability from a plain-text query.

Instructions

Look up cars by name or maker and say whether each is owned, its price and where it is sold.

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": {
      "query": "<query>"
    },
    "name": "gt7_find_car"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWords from the car name, e.g. "porsche 917"

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 establish a safe read-only, non-open-world operation, so the description's job is to add context. It does so by disclosing the returned fields (ownership, price, seller location), which is more than the annotations convey. It omits limits on result count or behavior for ambiguous or broad queries.

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?

A single front-loaded sentence covering both input and output with no filler or redundancy.

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 one-parameter read tool with no output schema, the description adequately covers what goes in and what comes back. Minor gaps remain around result volume and what happens when the query matches many or zero cars.

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 100% and the query parameter already carries a description with an example, so the baseline applies. The description adds a small amount by noting maker names work as a search basis, extending the schema's car-name-only example, but no further syntax or matching semantics are given.

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?

States a specific verb and resource ("Look up cars by name or maker") plus the payload it returns (owned status, price, where sold). It doesn't distinguish itself from siblings like gt7_missing_cars or gt7_in_stock_today, which cover related but different questions, 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?

The search basis (name or maker) is implied as the use case, which gives some guidance on when to reach for it. There is no explicit when-not or pointer to an alternative such as gt7_missing_cars for unowned cars or gt7_in_stock_today for availability.

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