Skip to main content
Glama

manufacturer_communications

Read-only

Search indexed NHTSA communications, with source coverage. Bulletins are not recalls.

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

Input Schema

NameRequiredDescriptionDefault
makeYes
yearYes
limitNo
modelYes
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds two useful behavioral facts beyond that: results carry source-coverage information, and bulletins are a distinct category from recalls. It says nothing about result volume, pagination limits, or what a sparse-coverage response looks like.

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?

Two short sentences, front-loaded with the core action, and the caveat follows immediately. Nothing is wasted, though "with source coverage" is terse enough to border on cryptic.

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?

A five-parameter search tool with zero schema descriptions, no output schema, and no parameter explanation leaves the agent guessing at filtering semantics and result shape. The description should do much more given how little structured data supports it.

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%, so the description carries the full burden for year, make, model, limit, and offset. It provides no meaning for any of them, not even confirming that year/make/model are the retrieval keys or explaining what limit/offset control.

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 indexed NHTSA communications") and adds a disambiguating clause that separates it from recall lookups. "Communications" itself is broad, but the recall caveat makes the intent usable.

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?

"Bulletins are not recalls" implicitly steers the agent to recall tools for recall data, which implies a when-not-to-use condition. However, there is no explicit statement of when this tool is the right choice, nor any named alternative.

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.