Skip to main content
Glama

Verify a North American VIN check digit

bpj_vin_north_america_check
Read-onlyIdempotent

Use North American VIN transliteration and position weights to verify the ninth character.

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": {
      "value": "<value>"
    },
    "name": "bpj_vin_north_america_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds algorithmic context (transliteration table plus position weights applied to the ninth character), which is genuinely informative, but it omits what happens on a failed check — an error versus a negative result — which matters for a verification tool.

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?

One sentence, front-loaded with the mechanism and result, with no filler. It is efficient, though the extreme brevity leaves several questions an agent would have unanswered.

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?

There is no output schema, so the description should state what the tool returns — a boolean, a corrected check digit, or an error — and it does not. For a simple one-parameter verification tool this is a noticeable but not fatal gap.

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 description coverage is 0%, and the single parameter is generically named 'value' with only a maxLength of 240, so the description must carry the meaning. It implies the input is a VIN string via 'North American VIN ... ninth character', but never states the required 17-character length or the treatment of I/O/Q, leaving real ambiguity.

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 names a specific verb ('verify') and a specific resource ('the ninth character' of a North American VIN), so the agent knows exactly what operation is being performed. It does not explicitly contrast itself with the many sibling check-digit tools, but the domain is unambiguous.

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 only implied: the 'North American VIN' qualifier signals it is not for European or other VIN formats, which is useful scoping. There is no explicit statement of when to call this versus when not, and no mention of prerequisites such as requiring a full 17-character VIN.

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.