Loading ToolBench

Reading the current corpus…

vin-lookup-mcp MCP server · D · ToolBench

← Browse

vin-lookup-mcp

github.com/taimoorgit/vin-lookup-mcp

MCP server for decoding VINs and fetching Canadian vehicle specs from NHTSA vPIC.

2026-07-28+STDIO2 tools

54/100

Definition Quality75

Protocol Readiness50

Supportability21

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence

Current-spec patterns detected

Summary

Two tools with clear verb-noun naming (decode_vin, get_canadian_vehicle_specifications) and reasonable descriptions (60-80 chars). Input schemas are present with typed parameters and descriptions. However, output schemas are not documented, the code returns complex nested dicts (summary, raw, specs_map, results) without formal schema declarations. Parameter descriptions lack format constraints and validation guidance. Error handling is present but generic ('NHTSA API returned no results') without recovery hints. No tool annotations (readOnlyHint, idempotentHint) despite both being read-only operations.

Tools (2)

decode_vinread onlysource verified77/100

Decode a 17-character vehicle VIN using NHTSA's free vPIC API.

get_canadian_vehicle_specificationsread onlysource verified72/100

Get Canadian vehicle specifications from NHTSA vPIC by year, make, and optional model.

Issues (5)

HIGHtool ↗

Output schemas not documented. Both tools return complex nested structures (summary, raw, specs_map, results) with no formal schema declaration. LLMs cannot plan downstream operations or extract fields reliably.

decode_vinget_canadian_vehicle_specifications

HIGHconstrained-input ↗

Parameter descriptions lack format constraints. 'vin' parameter says '17-character' but does not mention the character set restriction (no I, O, Q). 'units' parameter accepts 'Metric' or 'US' but description does not clarify case sensitivity or default behavior.

decode_vinget_canadian_vehicle_specifications

MEDIUMrecovery-guide ↗

Error messages lack recovery guidance. 'NHTSA API returned no results for this VIN' does not tell the LLM what to do next (retry, ask user for clarification, try a different tool). Errors should guide the agent's next action.

decode_vinget_canadian_vehicle_specifications

Recommendations

Document output schemas formally. For decode_vin, specify: {vin: string, summary: {Make, Model, ModelYear, ...}, raw: {...}, api_error_code: string|null, api_error_text: string|null}. For get_canadian_vehicle_specifications, document the structure of specs_map and results array.
Add format constraints to parameter descriptions. Change 'vin' description to: 'A 17-character VIN using digits and letters A-H, J-N, P-Z (no I, O, Q).' Change 'units' to: 'Units for specifications: "Metric" (default) or "US" (case-insensitive).'
Enhance error messages with recovery hints. Replace 'NHTSA API returned no results' with 'No vehicle found for VIN {vin}. Verify the VIN is correct (17 chars, no I/O/Q) and try again.' Replace 'NHTSA API request failed' with 'NHTSA service unavailable (HTTP {code}). Retry in 30 seconds or contact support.'
Add tool annotations. Mark both tools with readOnlyHint=true in the tool definition to signal they are safe to retry and do not modify state.
Add pagination to get_canadian_vehicle_specifications. Accept optional limit (default 20, max 100) and offset parameters. Return total count and next_offset in response. Document in description: 'Returns up to 20 results; use offset for pagination.'

Score history

Overall score trend

First recorded score · v2 rubric

54/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	D	54	2026-07-28+	v2