Skip to main content
Glama

nhtsa-vehicle-safety-mcp-server

by io.github.cyanheads

Nhtsa Search Investigations

nhtsa_search_investigations
Read-only

Search NHTSA defect investigations from the ODI flat file — covering Preliminary Evaluations (PE), Engineering Analyses (EA), Defect Petitions (DP), Recall Queries (RQ), Audit Queries (AQ), and additional ODI types. make, model, and component are structured filters against the investigation record's vehicle associations. All filters are ANDed. Use nhtsaId to fetch one investigation by its exact ID — including the investigationId nhtsa_search_recalls returns for a campaign. Investigations may link to a resulting recall campaign via recallCampaign.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
makeNoStructured filter — matches against the investigation's associated vehicle makes (e.g., "TOYOTA"). ANDed with other filters.
limitNoMax investigations to return. Defaults to 20; max 25. The cap is lower than the other paginated tools because a single investigation summary can run several thousand characters and is rendered in full.
modelNoStructured filter — matches against the investigation's associated vehicle models. ANDed with other filters.
queryNoFree-text search across investigation ID, subject, and summary.
offsetNoPagination offset into the matching investigations. Defaults to 0.
statusNoFilter by status: "O" (Open) or "C" (Closed). Omit to include both.
nhtsaIdNoExact NHTSA investigation ID (e.g. "EA23003"), case-insensitive. Fetches that one record — mutually exclusive with every other filter.
componentNoStructured filter — matches against the investigation's affected components (e.g., "STEERING"). ANDed with other filters.
investigationTypeNoFilter by ODI investigation type code (the leading letters of the NHTSA ID). Named types: "PE" (Preliminary Evaluation), "EA" (Engineering Analysis), "DP" (Defect Petition), "RQ" (Recall Query), "AQ" (Audit Query). Additional valid codes present in the dataset: "SQ", "EQ", "RP", "ID", "TA", "C". Pass any code exactly as it appears in the investigation ID prefix.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
limitNoPagination limit used for this page
noticeNoGuidance when no investigations match the filters, or when the requested page overshoots the result set.
offsetNoPagination offset used for this page
returnedNoNumber of investigations in this page
totalCountNoTotal matching investigations
effectiveQueryNoApplied filters as a readable string, e.g. make="Ford" status="O".
investigationsNoMatching investigations

TDQS

A4.3/5.0
Behavior4/5

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

The readOnlyHint annotation already signals safety, and the description adds valuable behavior details such as pagination (`offset`, `limit`) and the mutual exclusivity of `nhtsaId` with other filters, plus the case-insensitive fetching of a single record. This goes beyond the annotation without contradicting it.

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 dense but every sentence contributes: purpose, filter types, mutual exclusivity, and pagination details. It is well-structured, front-loaded with the core purpose, and avoids redundancy or filler.

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?

The description fully equips a user to call the tool: it covers all filters, explains mutual exclusivity, pagination behavior, investigation type codes, and the single-record fetch mode. Since an output schema exists, return values need not be described. No critical usage gaps remain.

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?

All nine parameters have schema descriptions (100% coverage), and the description adds extra semantics beyond those: `nhtsaId` is case-insensitive and mutually exclusive, `investigationType` explains the leading-letter prefix and lists additional valid codes, and `query` covers specific fields. This enriches parameter understanding beyond the raw schema.

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?

The description clearly states the tool searches NHTSA defect investigations from the ODI flat file, listing coverage of specific investigation types (PE, EA, DP, RQ, AQ, and additional types). It uses a specific verb and resource, making its intent unambiguous and distinct from sibling tools like recalls or complaints.

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?

The description explains the tool's scope and filter behavior but does not explicitly mention when to use it over sibling tools (e.g., search_recalls) or provide exclusions. While the coverage types imply a focused use case, explicit guidance on alternatives is missing.

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

All nhtsa-vehicle-safety-mcp-server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation4/5

Tools are mostly distinct, but nhtsa_get_safety_ratings and nhtsa_get_vehicle_safety overlap, with the latter subsuming the former. Descriptions help clarify when to use each, so agents are unlikely to misselect.

Naming Consistency5/5

All tools consistently use the nhtsa_ prefix followed by a verb_noun pattern (decode_vin, get_safety_ratings, lookup_vehicles, search_recalls). The verb varies by action but follows a predictable, uniform structure.

Tool Count5/5

Seven tools is well within the ideal range and fits the NHTSA vehicle safety domain. Each tool covers a distinct facet (VIN, ratings, complaints, recalls, investigations), justifying its presence without bloat.

Completeness4/5

The set covers core vehicle safety workflows: VIN decoding, safety ratings, complaints, recalls, and investigations. A minor gap is the lack of a dedicated tool for detailed recall or investigation record retrieval beyond search, but the existing search tools appear sufficient for most use cases.

Resources