Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

osint_ean_upc_validator

Read-onlyIdempotent

Validate EAN/UPC barcodes by recomputing the GS1 check digit, or generate the missing check digit for a partial code. Auto-detects format and derives country prefix and product segments.

Instructions

EAN / UPC Barcode Validator. Validate EAN-13, EAN-8, UPC-A, and UPC-E retail barcode numbers by recomputing the GS1 check digit, or (mode "generate") compute the missing check digit for a partial code. Auto-detects format from digit length (8/12/13) and, for EAN-13/UPC-A, derives the GS1 country prefix and manufacturer/product segments. Use this for the bare numeric string when you already have the digits; use osint_barcode_scanner to decode a barcode from an image, osint_barcode_generator to render one, and osint_isbn_validator for book ISBNs. Pure local arithmetic: read-only, non-destructive, no lookup or network call, offline-capable, and rate-limited. Returns whether the checksum is valid, the detected type, and the calculated vs provided check digits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesThe barcode number to process. Non-digit characters are stripped. For validate: 8, 12, or 13 digits (an 8-digit code starting with 0 is treated as UPC-E). For generate: the body without its check digit (7 digits for EAN-8, 11 for UPC-A, 12 for EAN-13).
modeNovalidate verifies the full code's check digit; generate computes the check digit for a partial code.validate

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the request was processed.
modeNoThe mode used (validate or generate).
inputNoThe raw code string as received.
resultNoValidation result (mode validate) or generated check-digit result (mode generate).
Behavior5/5

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

Annotations already mark it as read-only and idempotent. The description adds transparency by detailing the local arithmetic nature, no network calls, offline capability, and what the tool returns (validity, type, check digits). No contradictions with annotations.

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?

The description is moderately concise, front-loading the purpose and then providing necessary details. Each sentence serves a purpose, though it could be slightly trimmed without losing information.

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

Completeness5/5

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

Given the tool's simplicity (2 params, clear output schema), the description covers all necessary aspects: purpose, input requirements, mode behavior, return values, offline capability, and sibling differentiation. Fully complete.

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% with detailed descriptions for 'code' and 'mode'. The description adds context such as auto-detection of format from length, and explains behavior per mode, which complements the schema. Slightly redundant with schema but still valuable.

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?

The description clearly states the tool's purpose: validating EAN/UPC barcodes by recomputing check digits or generating missing check digits. It specifies supported formats (EAN-13, EAN-8, UPC-A, UPC-E) and distinguishes from related siblings like osint_barcode_scanner and osint_isbn_validator.

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

Usage Guidelines5/5

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

Explicitly states when to use this tool (for bare numeric strings vs image decoding, rendering, or ISBN validation). Also notes it's read-only, offline-capable, and rate-limited, providing clear context for usage decisions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server