APIVerve

QR Code Generator

QRCodeGenerator

Read-only

QR Code Generator: QR Code Generator creates customizable QR codes with support for colors, gradients, logos, and various styling options. Generate professional QR codes for marketing, packaging, and digital experiences. (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": {
      "value": "<value>"
    },
    "name": "QRCodeGenerator"
  }
}

Input Schema

Name	Required	Description	Default
`logo`	No	URL of logo image to place in center of QR code
`size`	No	Size of the QR code in pixels (50-2048)	300
`type`	No	The type of data being encoded. Advanced types (wifi, vcard) are premium.	text
`color`	No	Foreground color as hex code (e.g., #000000)	#000000
`value`	Yes	The text or data to encode in the QR code
`format`	No	Output format. Vector formats (svg, webp) are premium.	png
`margin`	No	Margin around the QR code in pixels (0-100)	10
`dotStyle`	No	Style of QR code dots	square
`gradient`	No	Gradient configuration with type (linear, radial) and colorStops array
`logoSize`	No	Size of logo relative to QR code (0.1-0.5)	0.3
`logoMargin`	No	Margin around logo in pixels	5
`cornerDotStyle`	No	Style of corner dots	square
`backgroundColor`	No	Background color as hex code (e.g., #ffffff)	#ffffff
`cornerSquareStyle`	No	Style of corner squares	square

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

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is known. The description adds one genuinely new behavioral fact not present in annotations or schema: a cost of 10 credits per call, which matters for agent budget decisions, but it omits premium-tier gating details (which live in the schema) and says nothing about logo URL fetching behavior.

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

Conciseness3/5

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

Only two sentences, but the opening redundantly restates the title verbatim ('QR Code Generator: QR Code Generator creates...'), wasting the highest-value position. The cost note tacked onto the end is useful but buried in parentheses.

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

Completeness3/5

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

With an output schema available and annotations covering safety, the description needs mainly to state capability and cost, which it does. However, for a 14-parameter premium-tiered tool it gives no sense of which options are gated, and the premium hints exist only inside the schema field descriptions.

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 description coverage is 100%, so all 14 parameters are already documented in the schema, and the description merely echoes the same feature list (colors, gradients, logos). With the schema doing the heavy lifting, the baseline of 3 is appropriate; no extra syntax or constraints are added.

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?

States a specific verb and resource (creates QR codes) plus the differentiating capability set: colors, gradients, logos, and styling options. It does not distinguish itself from sibling tools such as BarcodeGenerator or QRCodeReader, so it falls short of a 5.

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

Usage Guidelines2/5

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

The description names use contexts (marketing, packaging, digital experiences) but that is implied use, not routing guidance. It never says when to choose this over BarcodeGenerator for non-QR codes or QRCodeReader for decoding.

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.