Skip to main content
Glama

Tesla VIN Report

Explain a Tesla option code

explain_tesla_option_code
Read-onlyIdempotent

Explain one Tesla factory option code, such as APPF, APFB, APH4, BT85 or SC01. Use it when someone asks what a code on a Tesla's build sheet or listing means. Returns the meaning in plain English, what it means for a buyer where known, related codes and a page to read more. It does not look up any car. A code with no explanation here returns the error unknown_code.

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": {
      "code": "<code>"
    },
    "name": "explain_tesla_option_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesOne factory option code, for example APPF or BT85.

Output Schema

NameRequiredDescriptionDefault
okYes
urlNo
codeNo
noteNo
errorNo
knownNo
limitNo
titleNo
familyNo
meaningNo
messageNo
relatedNo
wordingNo
asked_forNo
codes_urlNo
disclaimerNo
for_a_buyerNo
wording_noteNo
retry_after_sNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description still adds real value: what comes back (plain-English meaning, buyer implications, related codes, a further-reading page) and the failure mode (unknown_code). It stops short of describing response shape in depth, but an output schema exists, so that gap is minor.

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?

Four short sentences, front-loaded with the verb+resource, then trigger, then return shape, then failure mode. Nothing repeats the schema verbatim and every sentence carries new information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter lookup whose output schema is already defined, the description covers what an agent needs: what it does, when to reach for it, what it is not (a car lookup), what it returns in outline, and how it fails.

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 100% and the single parameter is already documented with examples, so the baseline is 3. The description adds meaning beyond the schema by stressing "one" code per call and by pairing the input with the returned unknown_code error, telling the agent what an unrecognized value looks like.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Explain one Tesla factory option code" gives a specific verb and resource, then backs it with concrete examples (APPF, APFB, BT85, SC01). The sentence "It does not look up any car" explicitly distinguishes it from the sibling check_tesla_vin, so an agent can route without opening either schema.

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?

The trigger is stated concretely: "Use it when someone asks what a code on a Tesla's build sheet or listing means." The exclusion ("does not look up any car") implicitly steers VIN/lookup requests to check_tesla_vin, but no sibling is named explicitly as the alternative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources