validate_gtin
Validate a GTIN / UPC / EAN barcode (GTIN-8/12/13/14) by its check digit. Catches mistyped product barcodes in inventory/catalog workflows. Pure-algorithm.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes |
commerce-validators
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4.6/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description notes 'Pure-algorithm', indicating no side effects, external calls, or mutations. Given no annotations, this fully discloses behavior as a safe, read-only computation.
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?
Two complete sentences, no redundancy. Every word adds value: verb, resource, context, and behavioral hint.
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?
Covers purpose, input, and behavior, but lacks output format details (e.g., boolean or validation result). Given no output schema, this is a minor gap.
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?
The single parameter 'code' is described as a GTIN such as GTIN-8/12/13/14, adding meaning beyond the schema's minimal 'Code'. This clarifies input format, though exact length/digit constraints are not specified.
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 validates GTIN/UPC/EAN barcodes by check digit, specifying the exact types (GTIN-8/12/13/14). This distinguishes it from sibling tools that validate other entities like email domains or routing numbers.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies use for checking barcode validity in inventory/catalog workflows, but does not explicitly state when not to use or provide alternatives beyond the sibling list.
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.
TDQS
A4.1/5.0
Disambiguation5/5
Each tool targets a distinct type of validation or calculation (email domain, payout, reorder point, payment split, ABA routing, EORI, EU VAT, GTIN, IBAN, VAT rate). There is no overlap in purpose, and descriptions clarify the specific identifier or operation.
Naming Consistency4/5
Most tool names use a verb_noun pattern (e.g., validate_aba_routing, check_email_domain), but some are noun phrases (payout_reconciliation, reorder_point, stripe_connect_split, vat_rate_by_country). While clearly descriptive, the verb-prefix inconsistency slightly reduces predictability.
Tool Count5/5
With 10 tools, the server covers a focused set of commerce validation and calculation tasks without being too sparse or overwhelming. Each tool serves a clear, independent purpose.
Completeness4/5
The tool set covers key commerce validations (email, bank routing, IBAN, VAT, EORI, GTIN) plus useful calculations (payout, reorder, payment split, VAT rates). Minor gaps exist (e.g., phone/address/credit card validation, currency conversion), but the coverage is coherent for the stated domain.