Skip to main content
Glama

validate_vin

Read-only

Quickly validate a VIN without calling any external APIs.

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_vin"
  }
}

Input Schema

NameRequiredDescriptionDefault
vinYesVIN to validate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuine behavioral context by stating no external API call is made, but it never says what validation checks (length, check digit, allowed characters) or what a failure looks like. Note a soft tension: openWorldHint=true suggests external interaction while the text claims none, though this is likely a default flag rather than a real contradiction.

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?

A single front-loaded sentence with no wasted clauses, and the local-execution benefit is placed where it will be read first. The adverb "Quickly" is mild filler but does signal the performance tradeoff against API-based siblings.

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

Completeness3/5

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

This is a low-complexity, single-parameter tool with annotations and full schema coverage, so most requirements are met. With no output schema, however, the description should say what a validation result looks like (boolean, error message, normalized VIN), which it omits.

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?

There is a single parameter at 100% schema description coverage, so the schema already documents the 'vin' field fully. The description adds no format, casing, or length expectations beyond it, which matches the baseline of 3 when the schema does the work.

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?

The description gives a specific verb and resource ("validate a VIN") plus the distinguishing trait that validation happens locally. It does not, however, separate this from the sibling decode_vin, so an agent must guess whether validation is a subset of decoding.

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

Usage Guidelines2/5

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

There is no explicit statement of when to use this instead of decode_vin or batch_decode, and no prerequisites or exclusions. The only implicit guidance is "quickly" and "without external APIs," which hints at a lightweight local check but never names the alternative.

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.