Skip to main content
Glama
UseCOS MCP Server

UseCOS MCP Server

by rivlosys

validate_iso_vin

Validates a 17-character VIN against ISO 3779 and US 49 CFR Part 565, checking the Position 9 check digit and decoding WMI, model year, and plant code.

Instructions

Validate a 17-character Vehicle Identification Number (VIN) under ISO 3779 and US 49 CFR Part 565, verifying the Position 9 check digit and decoding WMI, model year, and plant code.

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

Input Schema

NameRequiredDescriptionDefault
vinYes17-character VIN to validate and decode

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses the specific validations performed (check digit at Position 9, WMI/model year/plant decoding), but says nothing about failure behavior (error vs. a result with a valid=false flag), whether the call is read-only, or any rate limits.

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?

A single front-loaded sentence with no filler; every clause (standards, check digit, decoded components) contributes information an agent needs.

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 one-parameter validation tool this is nearly complete, and the mention of decoding WMI, model year, and plant code hints at the return content. With no output schema, however, the exact response shape and failure representation remain unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and there is only one parameter, so the schema already documents the input. The description reinforces the 17-character requirement and what the value is used for, but adds no format or normalization guidance (e.g., case handling, I/O/Q exclusion) beyond the schema.

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?

States a specific verb (Validate) and resource (17-character VIN), names the governing standards (ISO 3779, 49 CFR Part 565), and enumerates exactly what is checked: Position 9 check digit, WMI, model year, plant code. The sibling tools are unrelated financial calculators, so no differentiation is needed.

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 is implied by the verb and the 17-character constraint, but there is no explicit when-to-use or when-not-to-use guidance. It does not say how non-North-American VINs (which lack a meaningful check digit) are handled, nor what to do for inputs that fail validation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.