Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

osint_qr_code_generator

Read-onlyIdempotent

Build QR code payloads for plain text, URLs, WiFi, vCard, SMS, or email. Returns a ready-to-render image URL.

Instructions

QR Code Payload Builder. Build the encoded text payload for a QR code from one of six input types — plain text, a URL, WiFi credentials (WIFI:…), a vCard contact, an SMS draft, or a mailto email — and return a ready-to-render image URL. Use this to prepare QR content; use osint_qr_code_scanner to decode an existing QR image, osint_barcode_generator for UPC/EAN/Code128 barcodes, and security_totp_qr_generator for 2FA otpauth:// codes. The API call runs locally and is read-only, non-destructive, deterministic, and rate-limited (20 req/min anonymous); the returned serviceUrl points at the third-party api.qrserver.com renderer, which a client fetches separately to obtain the PNG. Returns the encoded content, its length, the normalized settings, and that render URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesPayload type to encode. Unknown values fall back to text. (qrType is accepted as an alias.)text
qrTypeNoAlias for type; used when type is absent.
inputsNoPer-type fields; only the object matching type is read.
settingsNoRendering options applied to the serviceUrl.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoTrue when the payload was built.
resultNo
Behavior5/5

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

The description adds context beyond annotations: non-destructive, deterministic, rate-limited (20 req/min anonymous), and explains the serviceUrl is a third-party renderer fetched separately. No contradiction with annotations.

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?

The description is well-structured and front-loaded with purpose, but is somewhat verbose. Every sentence adds value; could be slightly more concise.

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

Completeness5/5

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

Given complexity (nested objects, 4 parameters, output schema exists), the description covers the API flow, rate limits, third-party dependency, and return fields. Fully adequate.

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% with detailed descriptions for all properties. The description summarizes but adds little beyond the schema, e.g., mentioning encoding formats like 'WIFI:T:...'. Meets baseline.

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 it builds QR code payloads from six input types and returns a render URL. It distinguishes itself from siblings by naming them explicitly (osint_qr_code_scanner, osint_barcode_generator, security_totp_qr_generator).

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

Usage Guidelines5/5

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

Explicitly states when to use this tool ('prepare QR content') and when to use alternatives (decode, barcode, TOTP). Provides clear context for selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server