Tanod Images

utilpeek: make a 1-D barcode image (SVG or PNG)

make_barcode

Idempotent

utilpeek: make a 1-D barcode image. For QR codes use make_qr_code; to find the product behind a number use lookup_barcode_product. Returns svg (text, with width_mm/height_mm) or data_base64 (PNG, with width_px/height_px; output "url": a 24 h link), plus encoded and bytes. A supplied check digit (ean13, ean8, upca, isbn13) must be right: a wrong one is a 422 invalid_checksum (not charged) rather than silently encoding a different number. Every output is decoded again with an independent reader (ZXing-C++): the answer carries verified: true and decoded_text, and a symbol that does not decode to the requested value is a 500 verify_failed (not charged). Encoded locally; typically under 0.1 s. Price: USD 0.001. Free: 10 utilpeek calls per IP per UTC day. Docs: https://tanod.dev/learn/barcode-generator-api.html

Input Schema

Name	Required	Description	Default
`data`	Yes	Value to encode (see the type rules).
`text`	No	Print the human-readable line (default true).
`type`	No	Symbology (default code128).	code128
`format`	No	svg (text) or png (base64).	svg
`output`	No	base64 (default): inline. url: stored for 24 hours; link, metadata.	base64

Output Schema

Name	Required	Description
`svg`	No
`text`	No
`type`	No
`bytes`	No
`error`	No	Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
`format`	No
`source`	No
`encoded`	No
`verified`	No
`width_mm`	No
`width_px`	No
`height_mm`	No
`height_px`	No
`data_base64`	No
`verified_by`	No
`verify_note`	No
`content_type`	No
`decoded_text`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

changedInput schema / properties / output / description

Previous value: -"base64 (default): the file comes back inline as base64. url: the file is stored for 24 hours and the reply carries a download link (url, expires_at, bytes, content_type, sha256) instead of the base64, which keeps the file out of your context window."New value: +"base64 (default): inline. url: stored for 24 hours; link, metadata."

Changed4 schema fields changedOct 17, 2026

addedOutput schema / properties / decoded_text

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / verified

Added value: +{
+  "type": [
+    "boolean",
+    "null"
+  ]
+}

addedOutput schema / properties / verified_by

Added value: +{
+  "properties": {
+    "library": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "license": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": [
+    "object",
+    "null"
+  ]
+}

addedOutput schema / properties / verify_note

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed1 schema field changedOct 12, 2026

addedInput schema / properties / output

Added value: +{
+  "default": "base64",
+  "description": "base64 (default): the file comes back inline as base64. url: the file is stored for 24 hours and the reply carries a download link (url, expires_at, bytes, content_type, sha256) instead of the base64, which keeps the file out of your context window.",
+  "enum": [
+    "base64",
+    "url"
+  ],
+  "title": "Output",
+  "type": "string"
+}

Changed1 schema field changedOct 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "bytes": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "content_type": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "data_base64": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "encoded": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "error": {
+      "description": "Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object."
+    },
+    "format": {
+      "enum": [
+        "svg",
+        "png",
+        null
+      ],
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "height_mm": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "height_px": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "source": {
+      "properties": {
+        "library": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "license": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "url": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "svg": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "text": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "type": {
+      "enum": [
+        "code128",
+        "ean13",
+        "ean8",
+        "upca",
+        "isbn13",
+        "code39",
+        null
+      ],
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "width_mm": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "width_px": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedOct 8, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well past the annotations: check-digit validation producing a 422 invalid_checksum, independent ZXing-C++ re-decode with verified/decoded_text, a 500 verify_failed on mismatch, and explicit 'not charged' guarantees. It also discloses latency (under 0.1 s), price (USD 0.001), and the free tier of 10 calls per IP per UTC day.

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?

Front-loaded with purpose and alternatives, then output shape, then error/pricing detail. Every sentence carries information, though the middle sentences are long and run together, costing some scannability.

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?

For a 5-parameter generation tool with an output schema, an agent still gets return fields, error codes, charge behavior, timing, and rate limits. Nothing needed to call it correctly or interpret a failure is missing.

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%, so the baseline is 3, but the description adds real meaning: it explains that `output` "url" yields a 24-hour link and that only certain symbologies (ean13, ean8, upca, isbn13) carry a check digit that must be correct. That goes beyond the enum labels.

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 and resource ('make a 1-D barcode image') and explicitly separates it from the QR tool (make_qr_code) and the lookup tool (lookup_barcode_product). An agent can route to it without opening any schema.

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?

Names the alternatives and the condition selecting each: QR codes go to make_qr_code, product lookups go to lookup_barcode_product. It doesn't cover the decode-side sibling (read_qr_barcode), but for the generate direction the routing is unambiguous.

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

All Tanod Images tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?