Skip to main content
Glama

Mechanic Atlas Auto Manual

NHTSA Owner Complaints

complaints
Read-onlyIdempotent

Owner complaints filed with NHTSA for a year, make and model: counts by component and the latest few.

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": "complaints"
  }
}

Input Schema

NameRequiredDescriptionDefault
makeYesMake, for example Toyota
yearYesModel year, for example 2015
modelYesModel, for example Camry

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description's real contribution is disclosing the return shape ('counts by component and the latest few'), which matters since there is no output schema, but 'the latest few' is vague about how many records come back. No mention of data source recency or rate limits.

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 dense sentence with the resource and the return shape front-loaded; nothing is redundant. Minor cost: 'the latest few' is too vague to be actionable and could have been stated as a count.

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 simple three-required-parameter read tool with full schema coverage and no output schema, the description covers source, scope and approximate result content. The only shortfall is the unspecified count and ordering of the 'latest few' complaints, which matters slightly more because no output schema exists to explain it.

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 each parameter already has an example (Toyota, 2015, Camry), so the schema does the heavy lifting. The description merely restates that year, make and model select the vehicle without adding format rules, ranges, or normalization guidance (e.g. make/model casing). Baseline 3 applies.

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?

Names a specific verb and resource ('Owner complaints filed with NHTSA') and scopes it precisely to a year/make/model lookup. It also states the shape of the result (counts by component plus the latest few), so an agent knows this is an aggregate complaint lookup rather than a raw document fetch. It does not differentiate itself from siblings like recalls, though the NHTSA-complaints framing is distinctive enough.

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 only implied: the presence of year/make/model signals a vehicle-specific lookup, and 'complaints' implicitly distinguishes it from recalls or repair guides. There is no explicit when-to-use statement, no prerequisites, and no mention of what to do if a vehicle is not found or of any alternative tool.

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.

Resources