Skip to main content
Glama

Create QR code

create_qr_code

Creates a stylized QR code from supplied text or a URL and an art-style description. Currently costs 0 credits. Starts a background job; returns a project id for wait_for_image_project. Before choosing settings, read get_account_info and the current parameter constraints. A listed model, resolution, duration or count is not necessarily available together or on this account. Preserve explicit requirements and all supplied inputs; explain a genuine block instead of submitting an incompatible request. Account balance alone does not prove a request is affordable.

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": {
      "content": "<content>",
      "style": "<style>"
    },
    "name": "create_qr_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOptional project name for identifying this output. Omit to use the API's default project name.Qr Code - dateTime
styleYesVisual art style for the QR code image.
contentYesThe content of the QR code.

Output Schema

NameRequiredDescriptionDefault
idYesUnique ID of the image. Use it with the [Get image Project API](https://docs.magichour.ai/api-reference/image-projects/get-image-details) to fetch status and downloads.
credits_chargedYesThe amount of credits deducted from your account to generate the image. We charge credits right when the request is made. If an error occurred while generating the image(s), credits will be refunded and this field will be updated to include the refund.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"Give your image a custom name for easy identification."New value: +"Optional project name for identifying this output. Omit to use the API's default project name."
    • addedInput schema / properties / style / description
      Added value: +"Visual art style for the QR code image."
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already say it mutates (readOnlyHint=false), is not idempotent, and is not destructive, so credit is for the extra context: it runs as a background job and returns a project id, and it currently costs 0 credits. Beyond that, the remaining sentences ("Preserve explicit requirements...", "Account balance alone does not prove a request is affordable") are generic policy text that could apply to any tool and disclose no behavior specific to this QR-code tool.

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?

The core is front-loaded and clear, but roughly half the text is reusable boilerplate about credits, constraints, and affordability that is not specific to creating a QR code. Those sentences add bulk and make it harder to find the tool-specific facts.

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?

An output schema exists and the async pattern is explained, so the description is complete enough to call the tool correctly: it covers inputs, background-job behavior, the follow-up tool, and the cost. It is short only on failure and retry behavior, which is a minor gap for a low-risk non-destructive creation tool.

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 schema already documents all three parameters, including the art-style template list. The description restates the inputs at a high level ("supplied text or a URL and an art-style description") without adding format, constraint, or default semantics, so it holds at baseline 3.

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?

The description gives a specific verb and resource ("Creates a stylized QR code from supplied text or a URL and an art-style description"), which is concrete enough that an agent can distinguish it from generic image generation. It does not, however, name a specific sibling that performs a similar but different job, and the two tools it does mention (get_account_info, wait_for_image_project) are supporting tools, not alternatives.

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 sets out the actual workflow: pre-check get_account_info and current constraints, then call this tool, then use the returned project id with wait_for_image_project. That covers when to use it and what to do next. It does not give any exclusion cases or say when to choose this over other image-producing siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.