APIVerve

Barcode Generator

BarcodeGenerator

Read-only

Barcode Generator: Barcode Generator creates downloadable barcode images from text or product codes in Code 128, Code 39, EAN-13, EAN-8, UPC-A, UPC-E, ITF-14, Codabar, MSI and other linear formats, with bar width, height and margin adjustable on paid plans. Each response provides a temporary image download link, the image size in pixels, file format, and expiration timestamp. (Cost: 10 credits)

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>",
      "type": "<type>"
    },
    "name": "BarcodeGenerator"
  }
}

Input Schema

Name	Required	Description
`data`	Yes	The data you want to generate a barcode from (string)
`type`	Yes	The type of barcode you want to generate
`height`	No	Height of the bars in pixels (default: 40)
`margin`	No	Quiet-zone margin around the barcode in pixels (default: 10)
`barWidth`	No	Width of the narrowest bar in pixels (default: 4)
`fontSize`	No	Font size of the text label in pixels (default: 20)
`lineColor`	No	The color of the barcode (default: #000000)
`textMargin`	No	Space between the bars and the text label in pixels (default: 2)
`displayValue`	No	Whether to display the value below the barcode (default: true)
`backgroundColor`	No	The background color of the barcode (default: #ffffff)

Output Schema

Name	Required	Description
`data`	No
`error`	No	Error message, null on success
`status`	No	"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description adds useful operational details beyond that: a 10-credit cost, a temporary download link with expiration, returned image size and format, and a paid-plan constraint on bar width/height/margin adjustments. It does not cover auth or rate limits, but is substantively helpful.

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 front-loaded and informative, with the core purpose, supported formats, output artifacts, and cost presented efficiently. The opening repeats the tool name twice ('Barcode Generator: Barcode Generator creates...'), which is unnecessary but minor.

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 10-parameter generator with full schema descriptions, annotations, and an output schema, the definition covers essential capabilities, output artifacts, cost, and one plan constraint. An agent has enough information to invoke it correctly without further research.

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 description coverage is 100%, so the schema documents all 10 parameters. The description adds some meaning by naming valid linear formats for 'type' and warning that barWidth, height, and margin are adjustable on paid plans. It does not explain validation rules per symbology or the color/text parameters, so it stays close to the schema baseline but adds useful context.

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 states a specific verb and resource ('creates downloadable barcode images from text or product codes'), enumerates supported linear symbologies, and thereby separates generation from reading or QR-code siblings. The scope is clear enough for an agent to identify the tool's role.

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?

The use case is implied clearly: generate barcode images from data. However, it gives no explicit when-to-use/when-not guidance, no alternatives such as BarcodeReader or QRCodeGenerator, and no prerequisite rules beyond the paid-plan note.

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

All APIVerve 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.