Skip to main content
Glama

Save a barcode

save_barcode

Save a barcode to QRdx, listed under Barcodes in the dashboard to edit and download later. Needs a QRdx API key with full access on this MCP connection (Authorization: Bearer qrdx_…); it saves to the key's workspace. Every plan saves barcodes (1,000 on Free). Takes the format and value generate_barcode takes, an optional title and options (foreground and background as hex, showText, barHeightMm, quietZone, scale, rotation).

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": {
      "value": "<value>",
      "format": "<format>"
    },
    "name": "save_barcode"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoA name to find it by, up to 100 characters (default: none; lists show the value)
valueYesThe number or text to encode, checked against the format's rules. Retail numbers can leave the check digit off and it's added.
formatYesThe symbology: ean13, ean8, upca, upce, code128, code39, code93, codabar, itf14, gs1-128, datamatrix, pdf417, aztec (EAN-13 and UPC-A for retail products, ITF-14 for cartons, GS1-128 for logistics labels, Code 128 for your own labels, Data Matrix, PDF417 and Aztec for 2D)
optionsNoHow it's drawn; anything left out uses the format's defaults (black on white, the minimum quiet zone, scale 4)
folderIdNoA folder of the workspace by id (the codes' folders); null for none

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / format / description
      Previous value: -"The symbology: ean13, ean8, upca, upce, code128, code39, codabar, itf14, gs1-128, datamatrix, pdf417, aztec (EAN-13 and UPC-A for retail products, ITF-14 for cartons, GS1-128 for logistics labels, Code 128 for your own labels, Data Matrix, PDF417 and Aztec for 2D)"New value: +"The symbology: ean13, ean8, upca, upce, code128, code39, code93, codabar, itf14, gs1-128, datamatrix, pdf417, aztec (EAN-13 and UPC-A for retail products, ITF-14 for cartons, GS1-128 for logistics labels, Code 128 for your own labels, Data Matrix, PDF417 and Aztec for 2D)"
  2. Changed1 schema field changed
    • changedInput schema / properties / format / description
      Previous value: -"The symbology: ean13, ean8, upca, upce, code128, code39, itf14, gs1-128, datamatrix, pdf417, aztec (EAN-13 and UPC-A for retail products, ITF-14 for cartons, GS1-128 for logistics labels, Code 128 for your own labels, Data Matrix, PDF417 and Aztec for 2D)"New value: +"The symbology: ean13, ean8, upca, upce, code128, code39, codabar, itf14, gs1-128, datamatrix, pdf417, aztec (EAN-13 and UPC-A for retail products, ITF-14 for cartons, GS1-128 for logistics labels, Code 128 for your own labels, Data Matrix, PDF417 and Aztec for 2D)"
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the auth requirement (API key with full access, Authorization: Bearer qrdx_…), that the record is scoped to the key's workspace, and the plan quota (1,000 barcodes on Free). That is exactly the operational context annotations cannot express for a write tool.

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?

Four sentences, front-loaded with what happens and where, then auth, then quota, then parameters. Slightly wasteful where it re-lists option keys (foreground, background, showText, barHeightMm, quietZone, scale, rotation) already fully described in the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter write tool with a nested options object and no output schema, the description covers auth, workspace scoping, quota, and persistence semantics well. It does not say what comes back on success (an id, a URL, the record itself), which is the one notable gap given no output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents every parameter including the nested options. The description adds only the cross-reference that format/value match generate_barcode and a compressed restatement of the option names, which the schema states in more detail. Baseline 3 applies.

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?

"Save a barcode to QRdx" gives a concrete verb plus resource and destination, and adds where it lands (Barcodes in the dashboard, editable/downloadable later). It implicitly separates itself from generate_barcode by referencing that tool as the source of the same format/value, though it never states outright that generate_barcode does not persist.

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 frames the persistence use case clearly: keep a code so you can edit and download it later. Referencing generate_barcode's format and value tells an agent this is the follow-on persist step. There is no explicit when-not guidance or named alternative for cases where saving is unnecessary.

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.