qr-maker

create_template

Save custom QR code style presets with colors, dot styles, logos, and dimensions for consistent reuse across projects without affecting quota limits.

Instructions

Save a QR code style preset. Style presets store visual settings (colors, dot styles, logos, dimensions) that can be applied to any content via render_template. Styles are unlimited and do not count against your quota.

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": {
      "name": "<name>",
      "options": "<options>"
    },
    "name": "create_template"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Style preset name (1-255 chars)
`description`	No	Optional description (max 1000 chars)
`options`	Yes	QR styling options to save as preset (same as generate_qr style param)
`tags`	No	Optional tags for organization (max 20)
`is_public`	No	Whether this style is publicly visible. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 13, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool creates persistent presets ('store visual settings'), mentions quota implications ('do not count against your quota'), and hints at public visibility ('publicly visible' via is_public parameter). However, it doesn't cover important behavioral aspects like error conditions, response format, or whether creation is idempotent.

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 perfectly sized with two sentences that each earn their place. The first sentence states the core purpose, the second adds important contextual information about unlimited usage and quota implications. No wasted words or redundant information.

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 creation tool with 5 parameters, 100% schema coverage, but no annotations and no output schema, the description is adequate but has gaps. It explains the purpose and some behavioral context but doesn't describe what happens after creation (success response, error cases) or how the created template can be used beyond the render_template mention.

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 5 parameters thoroughly. The description adds minimal value beyond the schema - it only implies that 'options' parameter contains 'QR styling options' and mentions 'publicly visible' which relates to 'is_public'. Baseline 3 is appropriate when the schema does most of the work.

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 the specific action ('Save a QR code style preset'), the resource ('visual settings'), and distinguishes from siblings by explaining what style presets are and how they differ from quota-limited operations. It explicitly mentions application via 'render_template' which is a sibling tool.

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 clear context for when to use this tool ('store visual settings that can be applied to any content via render_template') and mentions that styles are unlimited and don't count against quota. However, it doesn't explicitly state when NOT to use it or name specific alternatives among siblings.

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