Skip to main content
Glama

vin_recall_status

Read-only

VIN-specific manufacturer-reported open and completed recall status. Tesla and Ford open/completed states; GM completed/closed states with explicit repair dates where supplied; Honda and Acura active safety recalls; Subaru completed/incomplete safety recalls; Volkswagen, Audi, Land Rover and Jaguar recalls as reported by each maker; Nissan positive open safety recalls; Mopar positive open records matched to the full VIN. Service programs are separate. Toyota, Hyundai and Kia require interactive official verification. Unknowns are never zero. Not a complete service history. Where the maker's reply describes the VIN (Volkswagen, Audi, Land Rover, Jaguar, Subaru, Honda/Acura), manufacturer_description gives the raw text and only the fields it states.

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": {
      "vin": "<vin>"
    },
    "name": "vin_recall_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
vinYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, yet the description still adds real behavioral context: makers differ in what states they report, unknowns are never zero, the result is not a complete service history, and manufacturer_description carries raw text with only the stated fields populated. With no output schema, this return-semantics detail is valuable; a fuller account of the response envelope would push it higher.

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?

The purpose is front-loaded in the first clause and every subsequent clause carries non-obvious per-maker coverage information, so little is wasted. The middle section is one long undifferentiated run-on across nine manufacturers, which is harder to scan than a short structured list would be.

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 tool with no output schema and non-uniform per-manufacturer semantics, the description covers the important asymmetries and interpretation traps (unknowns not zero, incomplete service history, interactive-verification makes). The main gap is the absence of any statement about the response structure beyond the manufacturer_description field.

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?

There is a single parameter at 0% schema description coverage, so the description must compensate. It partially does: 'VIN-specific' and 'matched to the full VIN' signal that a complete 17-character VIN (not a partial) is expected, but it never states format, normalization, or invalid-VIN behavior.

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 opening sentence gives a specific verb+resource+scope: 'VIN-specific manufacturer-reported open and completed recall status,' and the per-manufacturer enumeration makes the resource unmistakable. It does not name a sibling such as lookup_recalls or defect_investigations, so the agent must infer the boundary from the 'Service programs are separate' remark rather than an explicit routing statement.

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 through caveats: 'Toyota, Hyundai and Kia require interactive official verification' tells the agent this tool will not fully answer for those makes, and 'Service programs are separate' blocks a common misuse. However, there is no explicit when-to-use vs. when-not guidance against sibling recall/defect tools, and no stated prerequisites for the VIN.

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.