Skip to main content
Glama

Quality QR

by io.github.silly-geese

quality_qr_create

Create a new trackable QR code saved to your Quality QR account. Use this when the user wants to generate a QR code for a URL, WiFi network, contact card, calendar event, phone number, email, SMS, restaurant menu, app download link, or social media profile. The QR code is persisted with scan tracking and analytics. Returns an inline SVG image of the QR code.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoType-specific structured data. Use instead of 'content' for complex types. WiFi: {ssid: string, password?: string, encryption?: 'WPA'|'WEP'|'nopass', hidden?: boolean}. vCard: {firstName: string, lastName: string, email?: string, phone?: string, mobile?: string, organization?: string, title?: string, website?: string, address?: {street?, city?, state?, zip?, country?}}. Event: {title: string, startDate: string (YYYY-MM-DD), startTime?: string (HH:mm), endDate?: string, endTime?: string, location?: string, description?: string, allDay?: boolean}. Social: {platforms: [{name: string, url: string, label: string}], profileName?: string, bio?: string}. Email: {to: string, subject?: string, body?: string}. Phone: {number: string}. SMS: {number: string, message?: string}.
nameNoA human-readable name for the QR code, e.g. 'Office WiFi' or 'Spring Menu 2026'. Auto-generated as 'MCP: {type} {date}' if omitted.
typeYesQR code content type. 'url' for websites, 'wifi' for network credentials, 'vcard' for contact cards, 'email' for pre-filled emails, 'phone' for tap-to-call, 'sms' for pre-filled texts, 'text' for plain text, 'event' for calendar events, 'pdf' for document links, 'menu' for restaurant menus, 'app-store' for app download links, 'social' for social media profiles.
designNoOptional visual customization for the QR code.
contentNoThe content to encode. Required for url, text, pdf, menu, and app-store types. For url types, provide the full URL including https://. For other types, use the 'data' parameter instead.
isDynamicNoSet to true to create a dynamic QR code whose destination URL can be changed later without reprinting the physical code. Only works for URL-based types (url, pdf, menu, app-store, social). Default: false.

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries full disclosure burden. It states that the QR code is 'trackable', 'saved to your account', 'persisted with scan tracking and analytics', and 'Returns an inline SVG image'. This adds valuable behavioral context beyond the schema, though it omits potential side effects or required authentication.

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 three sentences, each earning its place: purpose, usage scenario, and key behavior/return. It is front-loaded and free of fluff or redundancy.

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 six parameters with nested objects and no output schema, the description covers the essential aspects: what it does, when to use it, persistence, tracking, and return format. It does not explain the 'data' vs 'content' split, but the schema does, so the description is sufficiently complete for tool selection.

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 the baseline is 3. The description does not add parameter-level detail beyond what the schema already provides; it merely lists supported types in prose. The schema's thorough descriptions of 'data', 'content', 'isDynamic', and 'design' carry the semantic weight.

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 opens with a specific verb and resource: 'Create a new trackable QR code saved to your Quality QR account.' It clearly distinguishes this as the creation tool among siblings like list, get, update, delete, and analytics, and enumerates the supported content types.

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 provides explicit 'Use this when...' guidance listing many use cases (URL, WiFi, contact card, calendar event, phone, email, SMS, menu, app link, social profile). It does not explicitly state when not to use it or name alternatives, but the context is clear enough for a creation tool.

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

All Quality QR toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a distinct action: create, read (list/get), update, delete, and analytics. There is no overlap or ambiguity between the tools.

Naming Consistency5/5

All tools follow the consistent pattern `quality_qr_<verb>`, using lowercase snake_case. The only non-verb is 'analytics', but it still fits the naming convention and is immediately understandable.

Tool Count5/5

Six tools is well within the ideal range for a QR code management service. Each tool covers a necessary operation without redundancy or bloat.

Completeness5/5

The set provides full CRUD coverage (create, list, get, update, delete) plus analytics, which is a natural extension for tracking QR codes. No significant gaps exist for the service's purpose.

Resources