Skip to main content
Glama

Validate ISBN, EAN, VIN, IMEI, ISIN and Luhn numbers

validate
Read-only

Checks the check digit and structure of an identifier with no network call: ISBN-10 and ISBN-13 (with ISBN-10 to 13 conversion), EAN-8, UPC-A, EAN-13 and GTIN-14 (with the GS1 prefix country), VIN (manufacturer code, region, model year), IMEI, ISIN (country) and a generic Luhn number. type=auto detects the type. Up to 50 comma-separated values give a results array. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
typeNoauto (default), isbn, ean, vin, imei, isin or luhn
valueYesThe identifier, or up to 50 comma-separated

Output Schema

NameRequiredDescriptionDefault
typeNo
countNo
partsNo
validNo
valueNo
invalidNo
resultsNo
subtypeNo
checkedAtNo
normalisedNo
expectedCheckDigitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "checkedAt": {},
      +    "count": {},
      +    "expectedCheckDigit": {},
      +    "invalid": {},
      +    "normalised": {},
      +    "parts": {},
      +    "results": {},
      +    "subtype": {},
      +    "type": {},
      +    "valid": {},
      +    "value": {}
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

With only readOnlyHint and openWorldHint supplied, the description carries most of the burden and does well: it discloses the offline/no-network execution, the 50-item batch ceiling, per-call pricing with x402 payment networks, and that failed calls are not charged. The 'no network call' wording sits slightly at odds with openWorldHint=true, but it reads as a clarification of determinism rather than a contradiction of the safety profile.

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?

Dense but front-loaded: capability, enumeration, and offline behaviour come first, then batch semantics, then cost. The parenthetical conversion/region notes are compact value adds rather than filler, though the single run-on sentence is heavy.

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?

An output schema exists, so return values needn't be explained. The description covers formats, type detection, batching, and billing, which is nearly everything an agent needs; only invalid-identifier handling within a batch is left 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 description coverage is 100%, so both parameters are already documented. The description adds only the 'auto' default behaviour and restates the 50-value comma-separated limit; it gives no syntax or format examples beyond what the schema provides.

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 ('Checks the check digit and structure') and enumerates every supported identifier family: ISBN-10/13, EAN-8, UPC-A, EAN-13, GTIN-14, VIN, IMEI, ISIN, and generic Luhn. An agent can tell exactly what this tool does without opening the schema.

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?

It gives useful calling context ('type=auto detects the type', up to 50 comma-separated values), but never says when to prefer it over the sibling 'vin' tool or when not to use it. Usage is implied by the format list rather than explicitly routed.

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