Skip to main content
Glama

UK Data for Agents

vehicle_manufacturer_details

Read-onlyIdempotent

Who is this vehicle manufacturer and where are they registered? Returns NHTSA registration details for manufacturers matching a name or manufacturer ID: legal and common name, trading names, address and country, manufacturer type (for example completed vehicle manufacturer, vehicle alterer, importer), vehicle types and weight classes, named principal and last update. For supplier research, KYB and procurement checks. Source: NHTSA vPIC. Name matching is partial, so expect related firms such as dealers; personal contact emails are left out. (cost: 1 credit)

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

Input Schema

NameRequiredDescriptionDefault
limitNointeger, optional, max manufacturers to return, 1-50, default 10
manufacturerNostring, required, manufacturer name (partial match, e.g. honda) or NHTSA manufacturer ID (e.g. 988)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), so the description correctly spends its words elsewhere: partial matching that surfaces related firms such as dealers, deliberate omission of personal contact emails, and a stated cost of 1 credit. The remaining gap is pagination/truncation behavior beyond the limit parameter, which is minor here.

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?

Front-loaded with a scoping question, then the return payload, then caveats and cost — a sensible order with no filler sentences. It is dense and list-like, but every clause carries distinct information rather than restating the name.

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?

With no output schema, the description compensates by enumerating the returned fields (legal/common name, trading names, address and country, manufacturer type, vehicle types and weight classes, principal, last update), plus source attribution, known false-positive behavior, privacy exclusion, and credit cost. An agent has enough to call it and interpret the result without further digging.

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?

Schema coverage is 100%, so the baseline would be 3, but the description adds real meaning beyond the schema's 'partial match, e.g. honda' by explaining the consequence: related firms such as dealers will appear in results. It also reinforces that the identifier may be either a name or a numeric NHTSA manufacturer ID.

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?

Opens with a specific framing question and states a concrete verb+resource: returns NHTSA registration details for manufacturers matching a name or manufacturer ID, then enumerates exactly which fields come back. It is clearly distinguishable from data-heavy siblings like vin_decode or vehicle_recalls, but it never explicitly distinguishes itself from wmi_manufacturer_lookup, which an agent could plausibly confuse it with.

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?

Provides use contexts ('supplier research, KYB and procurement checks'), which implies when to reach for it. However, it gives no when-not guidance and does not route the agent away from the closely related wmi_manufacturer_lookup or vin_decode siblings, leaving the choice to inference.

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