Skip to main content
Glama

UK Data for Agents

wmi_manufacturer_lookup

Read-onlyIdempotent

Who made the vehicle with this VIN prefix? Decodes a World Manufacturer Identifier (the first 3 characters of a VIN, or 6 for small makers whose third character is 9) to the manufacturer, make, vehicle type and broad region, and accepts a full 17-character VIN to read its prefix. For fleet, import, parts and used-car checks. Source: NHTSA vPIC. It identifies the maker only, not the specific vehicle; use a full VIN decoder for model and specification. (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": "wmi_manufacturer_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
wmiNostring, required, 3- or 6-character WMI (e.g. 1HG) or a full 17-character VIN

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

The annotations already establish that this is a safe, idempotent, open-world read operation. The description adds useful behavioral context beyond them: the NHTSA vPIC source, the limitation to maker identification, and a cost of 1 credit. It does not discuss error behavior or lookup latency, which keeps it from a 5.

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 front-loaded with a direct question and the core action, then adds scope, use cases, source and cost without redundant restatement. Every sentence contributes either selection guidance or invocation context.

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?

For a single-parameter lookup with no output schema, the definition covers purpose, input interpretation, limitations, alternatives, provider and cost. Nothing material for correct invocation is missing.

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 input format is already documented, but the description adds real meaning by explaining why six characters are accepted for small manufacturers whose third character is 9, and by confirming that a full 17-character VIN is read only for its prefix.

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 states a precise verb and resource: it decodes a WMI/VIN prefix to manufacturer, make, vehicle type and region. It explicitly distinguishes itself from a full VIN decoder, so an agent can separate it from sibling tools such as vin_decode and vehicle_manufacturer_details.

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

Usage Guidelines5/5

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

It names concrete use cases (fleet, import, parts, used-car checks) and explicitly says to use a full VIN decoder when model or specification is needed. This gives both when-to-use guidance and a clear alternative for the case this tool does not cover.

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