Skip to main content
Glama

Read a curated template's design

qr_get_template
Read-onlyIdempotent

Fetch one of the 118 curated templates together with its full design config (module and finder shapes, colours, frame, caption). Use it when the user liked a template but wants changes: read the config here, then pass it to qr_generate with their tweaks. qr_generate_from_template renders the template as-is.

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": {
      "templateId": "<templateId>"
    },
    "name": "qr_get_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
templateIdYesTemplate id from qr_list_templates. Numeric or slug, e.g. "luxury-gold".

Output Schema

NameRequiredDescriptionDefault
idYesTemplate id.
nameNoTemplate name.
configYesThe engine QrConfig for this template: the same fields qr_generate accepts, so it can be tweaked and re-rendered.
categoryNoTemplate category (business, social, wifi, ...).
descriptionNoOne-line description of the template.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is covered. The description adds real value beyond that by describing the payload shape and the read-then-mutate workflow with qr_generate. It does not mention whether the 118 templates are stable or how unknown ids fail, which keeps it off a 5.

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?

Three short sentences, each doing distinct work: what is returned, when to use it with the follow-up step, and which sibling to use instead. The purpose and the primary routing cue are front-loaded with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with an output schema and full annotation coverage, nothing an agent needs is missing: the return contents are summarized, the id source is named, and the chaining into qr_generate is spelled out. Return-value details can be deferred to the output schema.

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 coverage is 100% and the templateId property already documents the numeric-or-slug form with an example, so the description carries no additional parameter burden. Its only marginal contribution is the '118 curated templates' hint about the valid id space. Baseline 3 is appropriate when the schema does 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?

States a specific verb and resource ('Fetch one of the 118 curated templates') plus exactly what comes back (module and finder shapes, colours, frame, caption). It also distinguishes itself from qr_generate_from_template, so an agent can pick correctly without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger condition ('when the user liked a template but wants changes') and a concrete downstream sequence (read config here, pass to qr_generate with tweaks). It also names the sibling that handles the as-is case, qr_generate_from_template, so the when-not is covered.

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.