Skip to main content
Glama

Barcode Generator - EAN-13, EAN-8, UPC-A, Code 128, Code 39, ISBN

barcode_generator
Read-onlyIdempotent

Draw a print-ready barcode as PNG (base64) and SVG: EAN-13, EAN-8, UPC-A, ISBN-13 (check digit computed or verified), Code 128 and Code 39 for any text. Wrong length or check digit -> clear 400 error. Runs on our server, < 0.2 s. Free: 25 calls/day per IP. Paid: $0.001 per call via x402 at https://radarbg.com/x402/barcode-generator.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "type": "ean13",
      "value": "590123412345"
    },
    "name": "barcode_generator"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoean13, ean8, upca, code128, code39 or isbn13ean13
valueYesThe number or text to encode, e.g. 590123412345

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only cover safety (readOnly, idempotent, openWorld); the description adds substantive operational detail beyond them: server-side execution, <0.2 s latency, a hard rate limit of 25 calls/day per IP, a paid x402 fallback at $0.001/call with an endpoint, and the failure mode (HTTP 400) for invalid input. It also discloses the return encodings (base64 PNG, SVG), which matters since there is no output schema.

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 the verb, output format, and symbology list; each following sentence adds a distinct fact (validation error, latency, quota, pricing). It is dense rather than padded, though the marketing-toned pricing URL sentence could be compressed and is arguably not needed 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?

For a two-parameter tool with no output schema, the description covers what is produced (PNG base64 and SVG), what inputs are valid, what happens on bad input, and what operational limits apply. Nothing an agent needs to select or call it correctly 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 a baseline of 3 is already met, and the description adds real meaning: it clarifies that EAN-13/ISBN-13 check digits are 'computed or verified', implying a 12-digit value is acceptable, and that Code 128/Code 39 encode 'any text' while the numeric symbologies are length-constrained. It stops short of per-type length rules that would push this higher.

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 output ('Draw a print-ready barcode as PNG (base64) and SVG') plus the exact symbologies supported (EAN-13, EAN-8, UPC-A, ISBN-13, Code 128, Code 39). An agent can tell this apart from qr_code_generator or invoice_generator from the text alone, without opening the schema.

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

Usage Guidelines3/5

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

Usage context is implied by the enumerated symbologies and the input-validation rule ('Wrong length or check digit -> clear 400 error'), which tells the agent what inputs are legal. However, no alternative tool is named and no when-to-use/when-not-to-use guidance is given, notably when a QR code or another generator should be preferred.

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.

Resources