barcode-mcp

Generate QR code

generate_qr

Generate QR code PNG images from text or URLs, with adjustable scale and error-correction levels.

Instructions

Generate a QR code as a PNG image. Convenience wrapper around generate_barcode for QR.

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

Input Schema

Name	Required	Description
`data`	Yes	Text, URL or data to encode
`scale`	No	Pixel scale factor (default 4)
`eclevel`	No	Error-correction level (default M)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It discloses the output format (PNG) and its wrapper relationship to generate_barcode, but does not mention side effects, error behavior, or limitations. For a simple generation tool, this is acceptable but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is only two sentences, with the core action in the first sentence and the sibling relationship in the second. No filler or redundant information.

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?

Given the simple 3-parameter schema and full schema coverage, the description provides enough context to understand the tool's purpose and output. The lack of output schema means return format is implied by 'PNG image', which is adequate but not explicit.

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?

The input schema covers 100% of parameters with descriptions, so the baseline is 3. The description does not add further meaning to parameters like data, scale, or eclevel beyond what the schema already states.

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 clearly states the tool generates a QR code as a PNG image, using a specific verb and resource. It distinguishes itself from generate_barcode by explicitly calling itself a convenience wrapper for QR, so an agent knows this is the QR-specific option.

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?

The description mentions it is a convenience wrapper around generate_barcode for QR, implying that for QR code generation this tool is preferred over the more general generate_barcode. However, it does not explicitly state when to use alternatives like bulk_barcode or decode_barcode, so guidance is helpful but not fully explicit.

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

Deploy Server