QR Branding

List QR design templates

qr_list_templates

Read-onlyIdempotent

List the 118 pre-designed QR templates (id, name, description, preview thumbnail URL). Filter by category if the user asks for a specific style.

Input Schema

Name	Required	Description	Default
`category`	No	Optional category filter (e.g. "business", "social", "wifi"). Omit to list all 118 templates.

Output Schema

Name	Required	Description
`total`	Yes	Number of templates returned.
`category`	No	The category filter applied, if any.
`templates`	Yes	The templates, after the optional category filter.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "category": {
+      "description": "The category filter applied, if any.",
+      "type": "string"
+    },
+    "templates": {
+      "description": "The templates, after the optional category filter.",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "category": {
+            "type": "string"
+          },
+          "description": {
+            "type": "string"
+          },
+          "id": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "number"
+              }
+            ],
+            "description": "Template id, for qr_generate_from_template."
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Number of templates returned.",
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "templates",
+    "total"
+  ],
+  "type": "object"
+}

First observedOct 9, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered without the description. The description adds the fixed catalog size (118) and the returned fields, which is modest extra context but nothing about pagination, ordering, or freshness of the template list.

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?

Two sentences, front-loaded with the core action and count, with no filler. The enumeration of return fields is partly redundant given an output schema exists, which is the only wasted space.

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?

For a one-parameter, read-only listing tool with an output schema, the description supplies purpose, scope (118 templates), and filter behavior, so an agent can call it correctly. The missing piece is the relationship to qr_generate_from_template, which would have made the surrounding workflow explicit.

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% for the single category parameter, and the schema already documents example values and the omit-to-list-all behavior. The description's restatement ("filter by category if the user asks for a specific style") adds user-intent framing but no new syntax or semantics, so the baseline 3 applies.

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?

States a specific verb and resource ("List the 118 pre-designed QR templates") plus the exact payload fields, so it is unmistakably the read-only catalog tool. It is clearly distinguishable from the build/generate siblings (qr_build_*, qr_generate*), which produce codes rather than enumerate designs.

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

Usage Guidelines3/5

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

"Filter by category if the user asks for a specific style" gives a condition for using the filter, which is real guidance but scoped only to the parameter. It never states when to call this tool versus its siblings, nor the obvious follow-on workflow (pick a template id here, then feed it to qr_generate_from_template), so usage is only implied.

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

All QR Branding tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?