API Ninjas

generateQRCode

Read-only

Generates a QR Code image for the specified data.

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>",
      "format": "<format>"
    },
    "name": "generateQRCode"
  }
}

Input Schema

Name	Required	Description	Default
`data`	Yes	Data to encode in the QR code.
`size`	No	Size of the QR code image to generate. The output will be a square image with (size x size) dimensions. The default size is 250.
`format`	Yes	Image format to return. Must be one of the following: png, jpg, jpeg, eps, svg.
`bg_color`	No	Background color of the QR code. Must be a 6-digit hex color (e.g. 00ff00 for green). Default is ffffff (white).	ffffff
`fg_color`	No	Foreground color of the QR code. Must be a 6-digit hex color (e.g. 00ff00 for green). Default is 000000 (black).	000000

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. Beyond that the description adds nothing: it does not disclose the return format (image bytes, base64, URL), whether encoding is local or remote, or any size/rate constraints. For a generation tool with no output schema, this is a real gap.

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?

A single front-loaded sentence with zero filler, which is appropriate for a simple one-purpose tool. It is arguably too terse, but there is no wasted structure or redundancy to penalize.

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

Completeness2/5

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

No output schema exists, so the description carries the burden of explaining what is returned, yet it never says whether the result is raw image data, a base64 string, or a URL. For an image-generation tool this omission leaves the agent guessing about how to use the output.

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%, with each of the five parameters (data, size, format, bg_color, fg_color) documented including enums, defaults, and hex patterns. The description adds no parameter meaning of its own, so the 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?

States a specific verb (Generates) and resource (QR Code image) with the input scope (specified data). An agent immediately knows what the tool produces. It does not, however, distinguish itself from the sibling generateBarcode, which follows the same pattern.

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?

There is no guidance on when to choose this tool over generateBarcode or any other generator sibling. No prerequisites, no context, no exclusions are given. The agent must infer usage entirely from the name.

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

All API Ninjas 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?