Skip to main content
Glama

nhtsa-vehicle-safety-mcp-server

Nhtsa Get Safety Ratings

nhtsa_get_safety_ratings
Read-only

Get NCAP crash test ratings and ADAS feature availability for a vehicle. Use when the user specifically wants crash test stars, rollover risk, or wants to compare safety features across vehicles. NCAP data available from 1990+, best coverage for 2011+.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nhtsa_get_safety_ratings"
  }
}

Input Schema

NameRequiredDescriptionDefault
makeNoVehicle manufacturer. Required with model and modelYear when vehicleId is omitted.
modelNoVehicle model. Required with make and modelYear when vehicleId is omitted.
modelYearNoModel year, a whole number. Required with make and model when vehicleId is omitted. NCAP coverage increases significantly for 2011+.
vehicleIdNoSpecific NCAP vehicle ID (from prior results). Mutually exclusive with active make/model/modelYear criteria.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
noticeNoGuidance when no NCAP ratings are found — coverage notes, adjacent years, and the lookup listing the model names NCAP files the vehicle under.
ratingsNoSafety ratings per vehicle variant

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedOutput schema / properties / notice / description
      Previous value: -"Guidance when no NCAP ratings are found — e.g. coverage notes or adjacent year suggestion."New value: +"Guidance when no NCAP ratings are found — coverage notes, adjacent years, and the lookup listing the model names NCAP files the vehicle under."
    • changedOutput schema / properties / ratings / items / properties / adasFeatures / properties / electronicStabilityControl / description
      Previous value: -"\"Standard\", \"Optional\", or \"Not Available\""New value: +"Electronic stability control: \"Standard\", \"Optional\", or \"No\""
    • changedOutput schema / properties / ratings / items / properties / adasFeatures / properties / forwardCollisionWarning / description
      Previous value: -"Forward collision warning availability"New value: +"Forward collision warning: \"Standard\", \"Optional\", or \"No\""
    • changedOutput schema / properties / ratings / items / properties / adasFeatures / properties / laneDepartureWarning / description
      Previous value: -"Lane departure warning availability"New value: +"Lane departure warning: \"Standard\", \"Optional\", or \"No\""
  2. Changed3 schema fields changed
    • changedInput schema / properties / vehicleId / description
      Previous value: -"Specific NCAP vehicle ID (from prior results). Skips the year/make/model lookup."New value: +"Specific NCAP vehicle ID (from prior results). Mutually exclusive with active make/model/modelYear criteria."
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `missing_required_combo`: Neither vehicleId nor a complete vehicle triple was supplied. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `mode_conflict`: vehicleId was combined with active vehicle criteria. `missing_required_combo`: Neither vehicleId nor a complete vehicle triple was supplied. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / error / properties / data / properties / reason / examples
      Previous value: -[
      -  "missing_required_combo"
      -]New value: +[
      +  "mode_conflict",
      +  "missing_required_combo"
      +]
  3. 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": [
      +      "ratings"
      +    ]
      +  },
      +  {
      +    "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. Declared by this tool: `missing_required_combo`: Neither vehicleId nor a complete vehicle triple was supplied. Other values are possible when a failure originates below the handler.",
      +          "examples": [
      +            "missing_required_combo"
      +          ],
      +          "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: -[
      -  "ratings"
      -]
  4. Changed4 schema fields changed
    • changedInput schema / properties / modelYear / description
      Previous value: -"Model year. Required with make and model when vehicleId is omitted. NCAP coverage increases significantly for 2011+."New value: +"Model year, a whole number. Required with make and model when vehicleId is omitted. NCAP coverage increases significantly for 2011+."
    • 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"
  5. Changed2 schema fields changed
    • removedOutput schema / properties / message
      Removed value: -{
      -  "description": "Contextual guidance populated when no ratings are returned",
      -  "type": "string"
      -}
    • addedOutput schema / properties / notice
      Added value: +{
      +  "description": "Guidance when no NCAP ratings are found — e.g. coverage notes or adjacent year suggestion.",
      +  "type": "string"
      +}
  6. Changed3 schema fields changed
    • changedOutput schema / properties / ratings / items / properties / complaintsCount / description
      Previous value: -"Number of complaints on file"New value: +"Complaints linked by NHTSA to this specific NCAP record. Variant-scoped — for vehicle-level totals call nhtsa_search_complaints."
    • changedOutput schema / properties / ratings / items / properties / investigationCount / description
      Previous value: -"Number of investigations on file"New value: +"Investigations linked by NHTSA to this specific NCAP record. Variant-scoped — for vehicle-level totals call nhtsa_search_investigations."
    • changedOutput schema / properties / ratings / items / properties / recallsCount / description
      Previous value: -"Number of recalls on file"New value: +"Recalls linked by NHTSA to this specific NCAP record. Variant-scoped — for vehicle-level totals call nhtsa_search_recalls."
  7. Changed1 schema field changed
    • addedOutput schema / properties / ratings / items / description
      Added value: +"Safety ratings for a single vehicle variant"
  8. Changed1 schema field changed
    • addedOutput schema / properties / message
      Added value: +{
      +  "description": "Contextual guidance populated when no ratings are returned",
      +  "type": "string"
      +}
  9. Changed4 schema fields changed
    • changedInput schema / properties / make / description
      Previous value: -"Vehicle manufacturer."New value: +"Vehicle manufacturer. Required with model and modelYear when vehicleId is omitted."
    • changedInput schema / properties / model / description
      Previous value: -"Vehicle model."New value: +"Vehicle model. Required with make and modelYear when vehicleId is omitted."
    • changedInput schema / properties / modelYear / description
      Previous value: -"Model year. NCAP coverage increases significantly for 2011+."New value: +"Model year. Required with make and model when vehicleId is omitted. NCAP coverage increases significantly for 2011+."
    • removedInput schema / required
      Removed value: -[
      -  "make",
      -  "model",
      -  "modelYear"
      -]
  10. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotation readOnlyHint=true already establishes that this is a safe read operation. Beyond that, the description adds useful behavioral context about data coverage: NCAP data starts in 1990, coverage is best from 2011 onward, and ADAS feature availability is included. It does not discuss pagination or error behavior, but an output schema is present, so return-format details are less critical.

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?

The description is three sentences, front-loaded with purpose, followed by use criteria and then a coverage caveat. Every sentence earns its place, and there is no redundant or filler wording.

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?

With only four parameters, an output schema, full schema coverage, and a read-only annotation, the definition is nearly complete. The main remaining gap is that it does not clarify how vehicleId relates to the make/model/year alternative in prose, leaving that relationship to the schema.

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%, so the input schema already documents each parameter's meaning and its requirement relationships. The description adds a coverage note for modelYear, but the schema itself also states that NCAP coverage increases for 2011+. Therefore, it adds little meaning beyond what the schema provides, making the baseline 3 appropriate.

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 uses a specific verb and resource: it retrieves NCAP crash-test ratings and ADAS feature availability for a vehicle. It clearly states the data domain, but it does not distinguish this tool from the sibling nhtsa_get_vehicle_safety, which sounds closely related and could easily be confused with it.

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 clear conditions for use: when the user wants crash test stars, rollover risk, or a comparison of safety features across vehicles. What it lacks is an explicit exclusion or a referral to an alternative sibling when the request is not about NCAP safety ratings, so the agent must infer the boundary itself.

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.