Skip to main content
Glama

defect_investigations

Read-only

Search NHTSA model-year defect investigations with retained source variants and snapshot dates.

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

Input Schema

NameRequiredDescriptionDefault
makeYes
yearYes
limitNo
modelYes
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The phrase about retained source variants and snapshot dates adds useful provenance context about the result data, but says nothing about result volume, truncation, or how snapshot dates affect what is returned.

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?

A single well-formed sentence with the resource front-loaded and no filler. The trailing clause about source variants and snapshot dates is meaningful but jargon-heavy enough that it costs some clarity.

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

Completeness2/5

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

For a five-parameter search tool with no output schema and zero parameter documentation, the description is too thin. It never explains pagination, result caps, or the shape of a returned investigation, leaving key invocation details absent from every structured surface.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters, so the description carries the full burden and largely fails. It hints at year/make/model via model-year phrasing but explains nothing about the limit cap of 50, offset pagination, or expected value formats for make and model.

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?

States a specific verb and resource: search NHTSA model-year defect investigations. That distinguishes it from recall lookup siblings such as lookup_recalls by naming the investigations dataset, though it never names an alternative tool or draws the comparison explicitly.

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

Usage Guidelines2/5

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

No when-to-use, when-not-to-use, or alternative-tool guidance is given. An agent cannot tell from the description when to prefer this over lookup_recalls or manufacturer_communications, nor what preconditions (valid year/make/model combination) apply.

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.