Skip to main content
Glama

nhtsa-vehicle-safety-mcp-server

Nhtsa Get Vehicle Safety

nhtsa_get_vehicle_safety
Read-only

Get a comprehensive safety profile for a vehicle. Combines NCAP crash test ratings, recalls, a complaint summary, and the defect investigations covering the vehicle into a single response. Use as the default when asked about vehicle safety, reliability, or purchase decisions. Investigation rows omit summaries: read one with nhtsa_search_investigations by nhtsaId.

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": {
      "make": "<make>",
      "model": "<model>",
      "modelYear": "<modelYear>"
    },
    "name": "nhtsa_get_vehicle_safety"
  }
}

Input Schema

NameRequiredDescriptionDefault
makeYesNonblank vehicle manufacturer (e.g., "Toyota", "Ford"). Case-insensitive.
modelYesNonblank vehicle model (e.g., "Camry", "F-150"). Case-insensitive.
modelYearYesModel year, a whole number (e.g., 2020).

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
noticeNoGuidance when no section matched the vehicle, or when recalls or complaints matched nothing while another section had records; empty NCAP ratings or investigations alone never trigger it. NHTSA can file one vehicle under different model names in each dataset, so the notice names the lookup that lists them and the tag marking the names each dataset uses; empty investigations take any listed name.
recallsNoAll recalls for this vehicle when available
warningsNoWarnings about sections that could not be loaded from NHTSA
safetyRatingsNoCrash test ratings per vehicle variant (e.g., FWD vs AWD)
sectionStatusNoAvailability of each data section in this response
effectiveQueryNoThe vehicle queried, as "make model modelYear".
investigationsNoEvery defect investigation covering this vehicle, newest-opened first, when available. Rows omit summaries.
complaintSummaryNoSummary of consumer complaints

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedOutput schema / properties / investigations
      Added value: +{
      +  "description": "Every defect investigation covering this vehicle, newest-opened first, when available. Rows omit summaries.",
      +  "items": {
      +    "additionalProperties": false,
      +    "description": "A defect investigation covering this vehicle",
      +    "properties": {
      +      "closeDate": {
      +        "description": "Date the investigation closed (YYYY-MM-DD), if closed",
      +        "type": "string"
      +      },
      +      "investigationType": {
      +        "description": "Investigation type code, the letters that open the ID (e.g., \"PE\")",
      +        "type": "string"
      +      },
      +      "investigationTypeName": {
      +        "description": "Investigation type name (e.g., \"Preliminary Evaluation\"), or the code for a type without one",
      +        "type": "string"
      +      },
      +      "matchedModels": {
      +        "description": "Model names on the investigation's vehicle associations that carry this make, model, and model year. The model matches within a longer name, so \"Cherokee\" also matches \"GRAND CHEROKEE\".",
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "nhtsaId": {
      +        "description": "NHTSA investigation ID. Pass it to nhtsa_search_investigations as nhtsaId for the full summary.",
      +        "type": "string"
      +      },
      +      "openDate": {
      +        "description": "Date the investigation opened (YYYY-MM-DD)",
      +        "type": "string"
      +      },
      +      "recallCampaigns": {
      +        "description": "Recall campaigns NHTSA links to the investigation — pass any to nhtsa_search_recalls as campaignNumber",
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "status": {
      +        "description": "Status code: \"O\" (open) or \"C\" (closed)",
      +        "type": "string"
      +      },
      +      "statusName": {
      +        "description": "Status name",
      +        "type": "string"
      +      },
      +      "subject": {
      +        "description": "Investigation subject",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "matchedModels"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / properties / notice / description
      Previous value: -"Guidance when no section matched the vehicle, or when recalls or complaints matched nothing while another section had records. NHTSA can file one vehicle under different model names in each dataset, so the notice names the lookup that lists them."New value: +"Guidance when no section matched the vehicle, or when recalls or complaints matched nothing while another section had records; empty NCAP ratings or investigations alone never trigger it. NHTSA can file one vehicle under different model names in each dataset, so the notice names the lookup that lists them and the tag marking the names each dataset uses; empty investigations take any listed name."
    • addedOutput schema / properties / recalls / items / properties / notes
      Added value: +{
      +  "description": "NHTSA's recall notes as published: the defect description for many campaigns received before 2000, and NHTSA's hotline sentence on most received since 2010. Omitted when NHTSA sends none.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / sectionStatus / properties / investigations
      Added value: +{
      +  "description": "Availability of defect investigation data in this response. Unavailable when NHTSA's investigation file failed to load, or was still loading 30 s into the call.",
      +  "enum": [
      +    "available",
      +    "unavailable"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / properties / sectionStatus / required
      Previous value: -[
      -  "safetyRatings",
      -  "recalls",
      -  "complaints"
      -]New value: +[
      +  "safetyRatings",
      +  "recalls",
      +  "complaints",
      +  "investigations"
      +]
  2. Changed8 schema fields changed
    • changedOutput schema / properties / notice / description
      Previous value: -"Guidance when no NHTSA records matched the vehicle — e.g. how to verify make/model/year spelling."New value: +"Guidance when no section matched the vehicle, or when recalls or complaints matched nothing while another section had records. NHTSA can file one vehicle under different model names in each dataset, so the notice names the lookup that lists them."
    • changedOutput schema / properties / recalls / items / properties / consequence / description
      Previous value: -"Safety consequence"New value: +"Safety consequence. Omitted for older campaigns whose record leaves it blank."
    • changedOutput schema / properties / recalls / items / properties / remedy / description
      Previous value: -"Corrective action"New value: +"Corrective action. Omitted for older campaigns whose record leaves it blank."
    • changedOutput schema / properties / recalls / items / properties / summary / description
      Previous value: -"Recall summary"New value: +"Recall summary. Omitted for older campaigns whose record leaves it blank."
    • changedOutput schema / properties / recalls / items / required
      Previous value: -[
      -  "campaignNumber",
      -  "manufacturer",
      -  "component",
      -  "summary",
      -  "consequence",
      -  "remedy",
      -  "reportReceivedDate"
      -]New value: +[
      +  "campaignNumber",
      +  "manufacturer",
      +  "component",
      +  "reportReceivedDate"
      +]
    • changedOutput schema / properties / safetyRatings / items / properties / adasFeatures / properties / electronicStabilityControl / description
      Previous value: -"ESC availability"New value: +"Electronic stability control: \"Standard\", \"Optional\", or \"No\""
    • changedOutput schema / properties / safetyRatings / items / properties / adasFeatures / properties / forwardCollisionWarning / description
      Previous value: -"FCW availability"New value: +"Forward collision warning: \"Standard\", \"Optional\", or \"No\""
    • changedOutput schema / properties / safetyRatings / items / properties / adasFeatures / properties / laneDepartureWarning / description
      Previous value: -"LDW availability"New value: +"Lane departure warning: \"Standard\", \"Optional\", or \"No\""
  3. Changed4 schema fields changed
    • changedInput schema / properties / make / description
      Previous value: -"Vehicle manufacturer (e.g., \"Toyota\", \"Ford\"). Case-insensitive."New value: +"Nonblank vehicle manufacturer (e.g., \"Toyota\", \"Ford\"). Case-insensitive."
    • addedInput schema / properties / make / minLength
      Added value: +1
    • changedInput schema / properties / model / description
      Previous value: -"Vehicle model (e.g., \"Camry\", \"F-150\"). Case-insensitive."New value: +"Nonblank vehicle model (e.g., \"Camry\", \"F-150\"). Case-insensitive."
    • addedInput schema / properties / model / minLength
      Added value: +1
  4. Changed6 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedOutput schema / anyOf
      Added value: +[
      +  {
      +    "not": {
      +      "required": [
      +        "error"
      +      ]
      +    },
      +    "required": [
      +      "sectionStatus",
      +      "warnings",
      +      "effectiveQuery"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "error"
      +    ]
      +  }
      +]
    • addedOutput schema / properties / error
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Present when the call failed. Absent on success.",
      +  "properties": {
      +    "code": {
      +      "description": "JSON-RPC error code for this failure.",
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "data": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "reason": {
      +          "description": "Machine-readable failure mode.",
      +          "type": "string"
      +        },
      +        "recovery": {
      +          "additionalProperties": {},
      +          "description": "Actionable next step for the caller.",
      +          "properties": {
      +            "hint": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "hint"
      +          ],
      +          "type": "object"
      +        },
      +        "retryable": {
      +          "description": "Whether retrying may succeed.",
      +          "type": "boolean"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "message": {
      +      "description": "Human-readable description of what went wrong.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "code",
      +    "message"
      +  ],
      +  "type": "object"
      +}
    • removedOutput schema / required
      Removed value: -[
      -  "sectionStatus",
      -  "warnings",
      -  "effectiveQuery"
      -]
  5. Changed4 schema fields changed
    • changedInput schema / properties / modelYear / description
      Previous value: -"Model year (e.g., 2020)."New value: +"Model year, a whole number (e.g., 2020)."
    • addedInput schema / properties / modelYear / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / modelYear / minimum
      Added value: +-9007199254740991
    • changedInput schema / properties / modelYear / type
      Previous value: -"number"New value: +"integer"
  6. Changed8 schema fields changed
    • addedOutput schema / properties / effectiveQuery
      Added value: +{
      +  "description": "The vehicle queried, as \"make model modelYear\".",
      +  "type": "string"
      +}
    • addedOutput schema / properties / notice
      Added value: +{
      +  "description": "Guidance when no NHTSA records matched the vehicle — e.g. how to verify make/model/year spelling.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / recalls / items / properties / consequence
      Added value: +{
      +  "description": "Safety consequence",
      +  "type": "string"
      +}
    • addedOutput schema / properties / recalls / items / properties / manufacturer
      Added value: +{
      +  "description": "Vehicle/equipment manufacturer",
      +  "type": "string"
      +}
    • addedOutput schema / properties / recalls / items / properties / overTheAirUpdate
      Added value: +{
      +  "description": "OTA update availability when provided by NHTSA",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / recalls / items / properties / parkOutSide
      Added value: +{
      +  "description": "Park-outside advisory when provided by NHTSA",
      +  "type": "boolean"
      +}
    • changedOutput schema / properties / recalls / items / required
      Previous value: -[
      -  "campaignNumber",
      -  "component",
      -  "summary",
      -  "remedy",
      -  "reportReceivedDate"
      -]New value: +[
      +  "campaignNumber",
      +  "manufacturer",
      +  "component",
      +  "summary",
      +  "consequence",
      +  "remedy",
      +  "reportReceivedDate"
      +]
    • changedOutput schema / required
      Previous value: -[
      -  "sectionStatus",
      -  "warnings"
      -]New value: +[
      +  "sectionStatus",
      +  "warnings",
      +  "effectiveQuery"
      +]
  7. Changed3 schema fields changed
    • addedOutput schema / properties / complaintSummary / properties / componentBreakdown / items / description
      Added value: +"Complaint counts for a single component"
    • addedOutput schema / properties / recalls / items / description
      Added value: +"A single recall campaign"
    • addedOutput schema / properties / safetyRatings / items / description
      Added value: +"Safety ratings for a single vehicle variant"
  8. Changed2 schema fields changed
    • addedOutput schema / properties / safetyRatings / items / properties / sideCrash / properties / combinedBarrierPoleFront
      Added value: +{
      +  "description": "Combined barrier/pole front rating",
      +  "type": "string"
      +}
    • addedOutput schema / properties / safetyRatings / items / properties / sideCrash / properties / combinedBarrierPoleRear
      Added value: +{
      +  "description": "Combined barrier/pole rear rating",
      +  "type": "string"
      +}
  9. Changed3 schema fields changed
    • changedOutput schema / properties / recalls / description
      Previous value: -"All recalls for this vehicle"New value: +"All recalls for this vehicle when available"
    • addedOutput schema / properties / sectionStatus
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Availability of each data section in this response",
      +  "properties": {
      +    "complaints": {
      +      "description": "Availability of complaint data in this response",
      +      "enum": [
      +        "available",
      +        "partial",
      +        "unavailable"
      +      ],
      +      "type": "string"
      +    },
      +    "recalls": {
      +      "description": "Availability of recall data in this response",
      +      "enum": [
      +        "available",
      +        "partial",
      +        "unavailable"
      +      ],
      +      "type": "string"
      +    },
      +    "safetyRatings": {
      +      "description": "Availability of NCAP safety ratings in this response",
      +      "enum": [
      +        "available",
      +        "partial",
      +        "unavailable"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "safetyRatings",
      +    "recalls",
      +    "complaints"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "safetyRatings",
      -  "recalls",
      -  "complaintSummary",
      -  "warnings"
      -]New value: +[
      +  "sectionStatus",
      +  "warnings"
      +]
  10. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, so the safety profile is covered; the description adds the genuinely useful behavioral disclosure that investigation rows omit summaries and must be expanded via a sibling. It stops short of describing result completeness or what happens when a vehicle has no data, but the partial-data caveat is the trait most likely to mislead an agent and it is covered.

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?

Three sentences, no waste, and front-loaded: what it returns, when to prefer it, and the one caveat with its remedy. Each sentence delivers distinct information and the default-usage rule is placed before the edge-case caveat.

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?

An output schema exists, so the description need not explain return values, and the description still summarizes the four data sources being merged. Given only three well-documented required parameters and a read-only annotation, nothing an agent needs to select or invoke it correctly is missing.

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 description coverage is 100% and all three parameters are documented with examples and case-insensitivity notes, so the schema carries parameter semantics. The description adds no parameter-level detail (e.g., whether make/model must match exactly or how year affects coverage), so the baseline 3 applies.

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?

Names a specific verb and resource ("Get a comprehensive safety profile for a vehicle") and then enumerates exactly what the profile contains: NCAP crash test ratings, recalls, complaint summary, and defect investigations. That enumeration makes it clearly distinguishable from the single-domain siblings like nhtsa_get_safety_ratings and nhtsa_search_recalls.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States an explicit default rule: "Use as the default when asked about vehicle safety, reliability, or purchase decisions," which tells the agent when this aggregate tool should win over the narrower siblings. It also gives a concrete follow-up route ("read one with nhtsa_search_investigations by nhtsaId") for the case where the aggregate result is insufficient.

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.