OnlineCyberTools MCP (280+ filterable tools)

osint_barcode_generator

Read-onlyIdempotent

Validate barcode data for six symbologies and generate a render URL for image creation. Supports UPC-A, EAN-13, Code 128, Code 39, ITF-14, and Codabar.

Instructions

Barcode Payload Builder. Validate input for a 1D barcode and build a ready-to-render image URL for one of six symbologies: UPC-A (12 digits), EAN-13 (13 digits), Code 128 (alphanumeric, up to 80 chars), Code 39 (A-Z 0-9 and . - $ / + %, up to 43), ITF-14 (14 digits), or Codabar (starts/ends A-D, up to 16). Use this to prepare barcode content and a render URL; use osint_barcode_scanner to decode a barcode from an image, osint_qr_code_generator for 2D QR codes, and osint_ean_upc_validator to only checksum-verify a UPC/EAN without rendering. The API call runs locally and is read-only, non-destructive, deterministic, and rate-limited (20 req/min anonymous); the returned serviceUrl points at the third-party bwipjs-api.metafloor.com renderer, which a client fetches separately to obtain the image. Returns the normalized type, the cleaned data, a validity flag and message, checksum/format metadata, the normalized settings, and that render URL.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`type`	No	Barcode symbology. Unknown values fall back to code128. (barcodeType is accepted as an alias.)	code128
`barcodeType`	No	Alias for type; used when type is absent.
`data`	Yes	Value to encode; format depends on type (e.g. 12 digits for upc, 13 for ean13, alphanumeric for code128). Trimmed before validation. (inputData is accepted as an alias.)
`inputData`	No	Alias for data; used when data is absent.
`settings`	No	Rendering options applied to the serviceUrl; invalid values fall back to the listed default.

Output Schema

TableJSON Schema

Name	Required	Description
`success`	No	Whether the payload was built.
`result`	No	Barcode payload, validation, and render details.
`error`	No	Present only on failure; reason the payload could not be built.

Schema Changelog

Changes observed during successful MCP inspections.

Changed22 schema fields changedv0.5.1Jun 3, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / barcodeType

Added value: +{
+  "description": "Alias for type; used when type is absent.",
+  "enum": [
+    "upc",
+    "ean13",
+    "code128",
+    "code39",
+    "itf14",
+    "codabar"
+  ],
+  "type": "string"
+}

addedInput schema / properties / data / description

Added value: +"Value to encode; format depends on type (e.g. 12 digits for upc, 13 for ean13, alphanumeric for code128). Trimmed before validation. (inputData is accepted as an alias.)"

addedInput schema / properties / inputData

Added value: +{
+  "description": "Alias for data; used when data is absent.",
+  "type": "string"
+}

addedInput schema / properties / settings / additionalProperties
```
Added value: +false
```

addedInput schema / properties / settings / description

Added value: +"Rendering options applied to the serviceUrl; invalid values fall back to the listed default."

addedInput schema / properties / settings / properties / addQuietZone / default
```
Added value: +true
```
addedInput schema / properties / settings / properties / addQuietZone / description
```
Added value: +"Include the mandatory blank margin around the barcode."
```
addedInput schema / properties / settings / properties / height / default
```
Added value: +80
```

addedInput schema / properties / settings / properties / height / description

Added value: +"Barcode height in pixels (mapped to the renderer height scale)."

addedInput schema / properties / settings / properties / height / enum
```
Added value: +[
+  50,
+  80,
+  120,
+  150
+]
```
addedInput schema / properties / settings / properties / showText / default
```
Added value: +true
```
addedInput schema / properties / settings / properties / showText / description
```
Added value: +"Print the human-readable text below the barcode."
```
addedInput schema / properties / settings / properties / width / default
```
Added value: +2
```
addedInput schema / properties / settings / properties / width / description
```
Added value: +"Module scale factor for the rendered bars."
```
addedInput schema / properties / settings / properties / width / enum
```
Added value: +[
+  1,
+  2,
+  3,
+  4
+]
```

removedInput schema / properties / settings / required

Removed value: -[
-  "width",
-  "height",
-  "showText",
-  "addQuietZone"
-]

addedInput schema / properties / type / default
```
Added value: +"code128"
```

addedInput schema / properties / type / description

Added value: +"Barcode symbology. Unknown values fall back to code128. (barcodeType is accepted as an alias.)"

addedInput schema / properties / type / enum

Added value: +[
+  "upc",
+  "ean13",
+  "code128",
+  "code39",
+  "itf14",
+  "codabar"
+]

changedInput schema / required

Previous value: -[
-  "type",
-  "data",
-  "settings"
-]New value: +[
+  "data"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "error": {
+      "description": "Present only on failure; reason the payload could not be built.",
+      "type": "string"
+    },
+    "result": {
+      "description": "Barcode payload, validation, and render details.",
+      "properties": {
+        "bcid": {
+          "description": "bwip-js barcode identifier for the renderer (e.g. upca, ean13).",
+          "type": "string"
+        },
+        "checksumInfo": {
+          "description": "Check-digit/check-character scheme for this type.",
+          "type": "string"
+        },
+        "data": {
+          "description": "The trimmed input value that was validated.",
+          "type": "string"
+        },
+        "formatDescription": {
+          "description": "What the symbology is used for.",
+          "type": "string"
+        },
+        "formatHelp": {
+          "description": "HTML requirements/help snippet for this type.",
+          "type": "string"
+        },
+        "formatInfo": {
+          "description": "Short allowed-character/length summary.",
+          "type": "string"
+        },
+        "heightScale": {
+          "description": "Renderer height-scale value derived from settings.height.",
+          "type": "integer"
+        },
+        "industryUsage": {
+          "description": "Typical industries that use this symbology.",
+          "type": "string"
+        },
+        "inputLabel": {
+          "description": "UI label describing the expected input for this type.",
+          "type": "string"
+        },
+        "maxLength": {
+          "description": "Maximum allowed input length for this type.",
+          "type": "integer"
+        },
+        "placeholder": {
+          "description": "Example value for this type.",
+          "type": "string"
+        },
+        "serviceUrl": {
+          "description": "bwipjs-api.metafloor.com image URL a client fetches to render the barcode; empty string when data is missing or invalid.",
+          "type": "string"
+        },
+        "settings": {
+          "description": "The normalized rendering settings actually applied.",
+          "properties": {
+            "addQuietZone": {
+              "description": "Whether a quiet-zone margin is included.",
+              "type": "boolean"
+            },
+            "height": {
+              "description": "Applied height in pixels.",
+              "type": "integer"
+            },
+            "showText": {
+              "description": "Whether human-readable text is shown.",
+              "type": "boolean"
+            },
+            "width": {
+              "description": "Applied module scale (1-4).",
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        },
+        "type": {
+          "description": "Normalized symbology (upc, ean13, code128, code39, itf14, codabar).",
+          "type": "string"
+        },
+        "typeDisplay": {
+          "description": "Human-readable symbology name (e.g. UPC-A, Code 128).",
+          "type": "string"
+        },
+        "valid": {
+          "description": "Whether data is a valid value for type.",
+          "type": "boolean"
+        },
+        "validationMessage": {
+          "description": "Human-readable validation outcome.",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "success": {
+      "description": "Whether the payload was built.",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0May 31, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare read-only, non-destructive, idempotent. The description adds crucial behavioral context beyond annotations: the API call runs locally, is rate-limited (20 req/min anonymous), and the returned serviceUrl points to an external third-party renderer fetched separately. No contradictions.

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 well-structured, front-loaded with purpose, and each sentence adds value. However, it is slightly verbose (four sentences) and could be trimmed without losing essential information. Still, it is clear and not wasteful.

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 complexity (nested settings, multiple symbologies, output schema), the description covers everything: local API behavior, external renderer, rate limits, output fields (normalized type, cleaned data, validity flag, etc.). No gaps remain for effective tool usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant meaning: it explains validation rules per symbology (e.g., '12 digits for upc, 13 for ean13'), alias parameters, fallback behavior for unknown type, and the settings object. This helps the agent correctly format data and understand output structure.

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 builds a barcode payload and render URL, listing six specific symbologies with character constraints. It distinguishes itself from sibling tools osint_barcode_scanner, osint_qr_code_generator, and osint_ean_upc_validator by explicitly stating when to use each.

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?

The description provides explicit guidance: 'Use this to prepare barcode content and a render URL; use osint_barcode_scanner to decode..., osint_qr_code_generator for 2D QR codes, and osint_ean_upc_validator to only checksum-verify...' This clearly tells the agent when to use this tool versus alternatives.

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

Deploy Server