GadgetHumans API Hub

by io.github.scotia1973-bot

generate_qr_code

Generate QR code as base64 PNG image

Input Schema

Name	Required	Description	Default
`size`	No	Size in pixels (default: 300)
`text`	Yes	Text or URL to encode

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedOct 10, 2026

removedInput schema / properties / bgcolor

Removed value: -{
-  "default": "FFFFFF",
-  "title": "Bgcolor",
-  "type": "string"
-}

removedInput schema / properties / color

Removed value: -{
-  "default": "000000",
-  "title": "Color",
-  "type": "string"
-}

removedInput schema / properties / ecc

Removed value: -{
-  "default": "M",
-  "title": "Ecc",
-  "type": "string"
-}

removedInput schema / properties / format

Removed value: -{
-  "default": "png",
-  "title": "Format",
-  "type": "string"
-}

removedInput schema / properties / margin

Removed value: -{
-  "default": 4,
-  "title": "Margin",
-  "type": "integer"
-}

removedInput schema / properties / size / default
```
Removed value: -300
```
addedInput schema / properties / size / description
```
Added value: +"Size in pixels (default: 300)"
```
removedInput schema / properties / size / title
```
Removed value: -"Size"
```
addedInput schema / properties / text / description
```
Added value: +"Text or URL to encode"
```
removedInput schema / properties / text / title
```
Removed value: -"Text"
```

removedInput schema / title

Removed value: -"generate_qr_codeArguments"

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "generate_qr_codeOutput",
-  "type": "object"
-}New value: +null

First observedJul 13, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries full behavioral burden. It discloses the output format (base64 PNG) but omits default size behavior, error handling, determinism, or rate limits. Minimal beyond the schema.

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 efficient sentence that front-loads the action and output. It earns its place, though it could be more specific about the encoding target.

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?

For a simple two-parameter tool with full schema coverage and no output schema, the description is adequate but lacks behavioral details that would help an agent understand return format and edge cases.

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 fully documents both parameters including defaults. The description adds no parameter detail beyond stating the output format, so 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+resource ('Generate QR code') and specifies the output format ('base64 PNG image'), which is concrete and distinguishing. It doesn't reference siblings, but the purpose is unambiguous.

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?

No indication of when to use this tool versus alternatives like encode_base64 or generate_uuid. The encoding target (QR vs base64 string) is implied but no explicit usage guidance is given.

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

All GadgetHumans API Hub 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?