VIN/HIN pre-purchase report: open NHTSA recalls, complaints, investigations, title-brand & liens.
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Average 5/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of ambiguity or confusion between tools.
With a single tool, naming consistency is not applicable; no inconsistency can arise.
A single tool is slightly minimal but reasonable for a focused service like title checking, as the tool consolidates multiple data sources into one comprehensive report.
The tool covers VIN/HIN decoding, recalls, complaints, and provides sources for further title checks, but explicitly omits official title records, leaving minor gaps for users needing state/NMVTIS data.
vehicle_reportAInspectGenerate a pre-purchase report for a titled asset by VIN (cars, trucks, RVs, trailers, heavy equipment) or HIN (recreational boats). Returns open federal NHTSA recalls (severity-ranked), consumer-complaint crash/fire/injury/death counts, open investigations, VIN check-digit + factory decode, and the exact next-step sources for lien & title-brand. Public NHTSA/USCG data — not an official title record; lien/salvage need a state/NMVTIS check, which the report links.
| Name | Required | Description | Default |
|---|---|---|---|
| hin | No | 12-character Hull Identification Number (recreational boats). | |
| vin | No | 17-character VIN (cars/trucks/RVs/trailers/equipment). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations present, so description carries full burden. It discloses data sources (public NHTSA/USCG), limitations (not official title), and return items (recalls, complaints, investigations, decode, next-step sources). No hidden behaviors remain.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single paragraph but well-structured: main action first, then scope, then detailed contents, then caveats. Every sentence adds value without redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite no output schema, the description enumerates all return elements (recalls with severity ranking, complaint counts, investigations, VIN check-digit, decode, next-step sources), making the tool's output fully predictable.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with descriptions for 'vin' and 'hin' parameters. The description adds context on when to use each (VIN for land vehicles, HIN for boats) and the character lengths, enhancing understanding beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description specifies the tool generates a pre-purchase report for titled assets by VIN or HIN, lists vehicle types (cars, trucks, RVs, trailers, heavy equipment, recreational boats), and details the return data. The verb 'generate' and resource 'pre-purchase report' are clear.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states when to use the tool (pre-purchase check), what data it covers (public NHTSA/USCG), and importantly distinguishes it from official title records, advising a state/NMVTIS check for lien/salvage. It provides clear alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!