Skip to main content
Glama

Mark a GT7 car owned or not

gt7_set_owned

Mark a Gran Turismo 7 car as owned or removed using its ID or exact name to keep your garage tracker accurate; requires the owner token.

Instructions

Record that a car was bought (or removed). Give the car id from gt7_find_car, or a name that matches exactly one car. Needs the owner token.

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": {
      "car": "<car>"
    },
    "name": "gt7_set_owned"
  }
}

Input Schema

NameRequiredDescriptionDefault
carYesCar id, or words from its name
ownedNo

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 cover the safety profile (readOnly=false, destructive=false, closed-world), and the description adds context those annotations cannot: an owner token is required, and a name must resolve to exactly one car or presumably fail. It does not spell out what the failure mode is when a name is ambiguous or whether owned=false deletes data versus just un-flagging it, which keeps it off a 5.

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?

Three short sentences, front-loaded with the action, then the identifier rule, then the auth requirement, with no wasted wording. The closing 'Needs the owner token' is slightly clipped — it does not say where that token comes from — but it earns its place as a precondition.

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 two-parameter mutation tool with no output schema, the description covers the action, the identifier source and uniqueness rule, and the auth requirement. The remaining gap is the semantics of toggling off (whether the record is deleted or merely unmarked) and any success/failure response shape.

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 50%: `car` is documented in-schema, and the description genuinely adds to it by stating that a non-id value must match exactly one car, which is a uniqueness constraint the schema does not convey. However, the `owned` parameter is never named or explained — its meaning and default=true must be inferred from the phrase 'bought (or removed)'.

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 verb and resource — recording that a car was bought or removed — and the parenthetical makes clear this is a toggle in both directions. It points at gt7_find_car as the source of car ids, which implicitly separates it from the read-only lookup siblings, though it never names the alternative explicitly.

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?

It gives a clear precondition chain: obtain the id from gt7_find_car, or supply a name matching exactly one car, and have the owner token available. There is no explicit 'do not use this for X' statement, but the workflow context is strong enough that an agent knows when to reach for it.

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