Skip to main content
Glama

qr: QR codes that never expire

Create many QR codes

create_qr_codes_bulk

Create several codes at once, optionally in a new campaign (e.g. one code per poster location). Needs an API key; the maximum per call depends on the plan.

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": {
      "items": "<items>"
    },
    "name": "create_qr_codes_bulk"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
campaignNoOptional campaign name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, destructive=false, openWorld=false), the description adds two genuinely useful facts: an API key is required and the per-call maximum is plan-dependent. It does not say whether a bulk call is atomic or how partial failures are reported, which is the main remaining behavioral gap for a batch mutation.

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 compact sentences with the core action front-loaded and the auth/limit caveat second. No filler, though the plan-dependent maximum could be phrased more actionably (e.g. check get_limits).

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?

With no output schema, the description should say what a successful bulk call returns (created code IDs/URLs, or a per-item error list), and it does not. Auth requirements and plan-based caps are covered, so the definition is adequate but leaves an agent guessing about results and partial-failure semantics.

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 50%, with campaign already documented in the schema and the items sub-properties partially described. The description adds that campaign creates a new campaign and implies items maps one-to-one to codes, but it does not explain the title/target_url fields or any per-item validation limits.

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?

"Create several codes at once" states a specific verb and scope (bulk) that separates it from the singular create_qr_code sibling, and the campaign example clarifies the resource. It stops short of naming the single-create tool explicitly, so the distinction is inferred rather than stated.

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?

The parenthetical "one code per poster location" gives a concrete scenario that implies when to use it, and "optionally in a new campaign" clarifies the campaign parameter's intent. There is no explicit when-not guidance or pointer to create_qr_code for single codes or get_limits for quota checks.

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.