Create an editable (dynamic) QR code whose destination you can change later without reprinting. Requires an OpenQR API key.
| Name | Required | Description | Default |
|---|---|---|---|
| label | No | Optional label. | |
| theme | No | A saved theme id or name to style the code with. | |
| destination | Yes | The http(s) URL the code should point to. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose all behavioral traits. It only mentions creation and editability, but omits side effects (e.g., what is created/stored), return value format, potential failures, or rate limits. This is insufficient for safe invocation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise: two sentences that front-load the core purpose and a critical prerequisite. There is no unnecessary text, and every sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite having only 3 simple parameters and no output schema, the description does not mention what the tool returns (e.g., a QR code ID or image URL) or any limitations. An agent would lack core context about the invocation outcome, making the description incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 parameters adequately. The description adds no additional context for parameters such as format, constraints, or usage examples, so it remains at the baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool creates a dynamic QR code with editable destination, distinguishing it from static QR codes and siblings like 'generate_qr'. The verb 'create' and resource 'dynamic QR code' are explicit.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use it (when editability is needed) by contrasting with 'later without reprinting'. It also notes the API key requirement. However, it does not explicitly mention when not to use it (e.g., for non-editable codes use generate_qr) or compare to bulk_create_dynamic_qr.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct operation on a specific resource: static vs dynamic QR creation, single vs bulk, subdomain management, folder/theme CRUD, scan statistics. No two tools have overlapping purposes; even similar verbs like create_dynamic_qr and bulk_create_dynamic_qr are clearly differentiated by cardinality.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., create_dynamic_qr, get_scans, set_subdomain). Compound verbs like bulk_create are standard. No mixing of styles or irregular names.
17 tools is well-scoped for a QR code management server. It covers creation (static, dynamic, bulk), update, delete, retrieval, listing, scan stats, subdomain management, folders, and themes—each tool serves a clear purpose without bloat.
The toolset provides full CRUD for dynamic QR codes and subdomain management, plus scan statistics, folder and theme management. Minor gaps: missing update operations for folders and themes, and no search/filter tool for codes. These are acceptable omissions given the API's typical usage.