Skip to main content
Glama

BRAINIAC Vehicle VIN, Safety, Fuel Economy & On-Time

Validate a VIN check digit

vehicle-transport_vin-check-digit-validate
Read-onlyIdempotent

Validate the structure and 9th-position check digit of a 17-character VIN and read model-year code candidates from 49 CFR Part 565. Pure computation; no network. Price $0.01 USDC. POST /api/v1/vehicle-transport/vin-check-digit-validate. An unpaid call returns the x402 payment terms and does not run.

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": {
      "vin": "<vin>"
    },
    "name": "vehicle-transport_vin-check-digit-validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
vinYesvin, string, length 1 to 32. Required.

Output Schema

NameRequiredDescriptionDefault
vdsNovds. String.
vinNovin. String.
visNovis. String.
wmiNowmi. String.
validNovalid. Boolean.
lengthNolength. Number.
checkDigitNocheckDigit. Object.
modelYearCodeNomodelYearCode. String.
invalidCharactersNoinvalidCharacters. Array.
modelYearCandidatesNomodelYearCandidates. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior2/5

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

The description adds genuinely useful behaviour beyond annotations: regulatory basis (49 CFR Part 565), zero network dependence, a $0.01 USDC price with x402 terms for unpaid calls, and the fact that an unpaid call does not execute. However, 'Pure computation; no network' conflicts with the openWorldHint=true annotation, which is precisely the signal an agent uses to decide whether a call reaches external systems; that inconsistency is the main behavioural defect 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?

Four short, front-loaded sentences: what is validated first, then the computation/network trait, then payment terms and endpoint. Price and path could be seen as boilerplate, but for an x402-paid tool they carry decision-relevant information and are stated compactly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter, read-only validation tool with an output schema (so return shape need not be explained), the description covers origin of the rule, computation model and payment gating. The remaining gap is what a non-validating result means for inputs outside the 17-character format, which the output schema may partially cover.

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 baseline is 3, but the description adds real domain meaning the schema lacks: the VIN must be a 17-character string and the 9th position is the check digit, whereas the schema only says length 1–32. The 1–32 vs 17 discrepancy is not reconciled, which keeps it from a 5.

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?

Names a specific verb and resource: validate the structure and 9th-position check digit of a 17-character VIN, plus reading model-year codes per 49 CFR Part 565. That is precise enough to separate it from sibling 'vehicle-transport_vin-decode' (which would return decoded fields rather than a validity judgement), though the description never explicitly contrasts with that sibling.

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?

Usage context is implied by the narrow purpose (use when you need a check-digit/structural verdict on a VIN) and by the payment note, but there is no explicit when-to-use / when-not-to-use guidance, no statement about how it differs from vin-decode, and no indication of what happens on a malformed or non-17-character input.

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