ScorpTech x402 API

Barcode Generate

barcode_generate

Read-onlyIdempotent

Generate a 1D barcode as SVG (plus base64 data URI and the raw module pattern): Code 128 (any ASCII, automatic A / B / C subset switching for the shortest symbol), GS1-128 shipping / logistics labels from "(01)…(17)…(10)…" application identifiers (FNC1 separators, SSCC / GTIN check digits verified), EAN-13, EAN-8, UPC-A and ITF-14 (check digit computed when omitted, verified when given) and Code 39 (optional mod-43 check). Options: module width, bar height, quiet zone, human-readable text, colours. For product labels, shipping cartons, inventory and tickets. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/barcode-generate

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": "barcode_generate"
  }
}

Input Schema

Name	Required	Description	Default
`bg`	No		#ffffff
`fg`	No		#000000
`data`	Yes	Content to encode (digits for EAN / UPC / ITF)
`text`	No	Print the human-readable text under the bars
`type`	No		code128
`quiet`	No	Quiet zone each side (modules)
`scale`	No	Pixels per module
`height`	No	Bar height (px)
`checksum`	No	Code 39: append the mod-43 check character

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations, it discloses pricing ($0.002 USDC per successful call via x402 on Solana), the HTTPS endpoint alternative, and the exact output shape (SVG plus base64 data URI and raw module pattern). It also describes automatic check-digit computation/verification and Code 128 subset switching, which materially affects behavior.

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 every clause carries useful information, with no filler. It is a single dense run-on sentence, which slightly hurts readability but does not waste space.

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?

With 9 parameters, no output schema, and a paid x402 endpoint, the description provides everything an agent needs: supported symbologies, return format, cost/payment mechanism, and parameter-affecting behaviors. Nothing essential is missing.

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 only 67%, but the description compensates well: it explains that Code 39 has an optional mod-43 check, that EAN/UPC/ITF-14 check digits are computed when omitted and verified when given, and that options include module width, bar height, quiet zone, human-readable text, and colours. This adds real meaning beyond the schema for most parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a precise verb+resource: 'Generate a 1D barcode as SVG (plus base64 data URI and the raw module pattern)' and enumerates the supported symbologies. It clearly identifies the tool but does not explicitly name or distinguish itself from the nearby sibling qr_generate, leaving that inference to the agent.

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?

It gives concrete usage contexts ('product labels, shipping cartons, inventory and tickets') and maps symbologies to scenarios (EAN/UPC for retail, GS1-128 for shipping/logistics). However, it never states when not to use it or points to alternatives like qr_generate for 2D codes.

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

All ScorpTech x402 API 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?