Skip to main content
Glama

Image Resize & Convert Tools (Tanod)

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

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": {
      "data": "<data>"
    },
    "name": "make_barcode"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesValue to encode (see the type rules).
textNoPrint the human-readable line.
typeNoSymbology.code128
formatNosvg (text) or png (base64).svg
outputNobase64 (default): inline. url: stored for 24 hours; link, metadata.base64

Output Schema

NameRequiredDescriptionDefault
svgNo
textNo
typeNo
bytesNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
formatNo
sourceNo
encodedNo
verifiedNo
width_mmNo
width_pxNo
height_mmNo
height_pxNo
data_base64No
verified_byNo
verify_noteNo
content_typeNo
decoded_textNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • removedInput schema / properties / data / title
      Removed value: -"Data"
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / output / title
      Removed value: -"Output"
    • changedInput schema / properties / text / description
      Previous value: -"Print the human-readable line (default true)."New value: +"Print the human-readable line."
    • removedInput schema / properties / text / title
      Removed value: -"Text"
    • changedInput schema / properties / type / description
      Previous value: -"Symbology (default code128)."New value: +"Symbology."
    • removedInput schema / properties / type / title
      Removed value: -"Type"
    • removedInput schema / title
      Removed value: -"make_barcodeArguments"
    • removedOutput schema / properties / source / properties
      Removed value: -{
      -  "library": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "license": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "url": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  }
      -}
    • removedOutput schema / properties / verified_by / properties
      Removed value: -{
      -  "library": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "license": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "url": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  }
      -}
  2. Changed1 schema field changed
    • 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."
  3. Changed4 schema fields changed
    • 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"
      +  ]
      +}
  4. Changed1 schema field changed
    • 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"
      +}
  5. Changed1 schema field changed
    • 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"
      +}
  6. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), and the description goes well beyond it: exact return shapes (`svg` with width_mm/height_mm vs `data_base64` with width_px/height_px), the 24 h URL retention, checksum rejection as 422 invalid_checksum, independent ZXing-C++ re-decode yielding `verified`/`decoded_text`, 500 verify_failed, uncharged failures, sub-0.1 s local encoding, and pricing/free-tier limits. This is unusually rich behavioral context for a priced, verifiable operation.

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 sibling routing, then grouped into returns, error semantics, performance, and price/docs. Dense but nearly every sentence carries decision-relevant information; the pricing/free-tier appendage is useful for agent budgeting but makes the block longer than strictly necessary for correct invocation.

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?

Despite an existing output schema, the description supplies the error taxonomy (422 invalid_checksum, 500 verify_failed, neither charged) and verification guarantees that a schema alone would not convey. Combined with latency, cost, and docs reference, an agent has everything needed to call this correctly and interpret failures.

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; the description earns above that by explaining that a supplied check digit for ean13/ean8/upca/isbn13 must be correct and adding the 24-hour retention meaning for `output: url`. It leaves 'see the type rules' for `data` somewhat external, pointing at documentation rather than restating length/charset rules for code128/code39.

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 immediately scopes itself against its two nearest siblings: make_qr_code for QR codes and lookup_barcode_product for product lookup by number. An agent can choose this tool 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 Guidelines5/5

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

Explicitly names both alternatives and the condition that selects each ('For QR codes use make_qr_code; to find the product behind a number use lookup_barcode_product'). It also names the supported symbologies' checksum rules, so the agent knows which type choices carry obligations.

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.