Skip to main content
Glama

qr: QR codes that never expire

Change where a QR code leads

update_qr_code
Idempotent

Change the target URL (or title, or pause/activate) of an existing code. Printed copies keep working and now lead to the new target. Needs the API key of the owner or the edit_url of an anonymous code.

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": {
      "code": "<code>"
    },
    "name": "update_qr_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe short code, e.g. "k7Fq2" (the part after ?c= in the short URL)
titleNo
activeNofalse pauses the code (scanners see a friendly note)
edit_keyNoFor codes created without an API key: the edit_url (or its key) returned at creation
target_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover idempotency, non-destructiveness, and non-read-only status; the description adds genuinely new context that existing printed copies keep working and resolve to the new target, plus the auth requirement for owner keys vs. anonymous edit_urls. It stops short of describing what happens to fields not supplied or how the response looks.

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, front-loaded with the change operation, followed by the user-visible effect and the auth requirement. No filler or redundant restatement of the title.

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 five-parameter mutation tool with annotations and no output schema, the description covers purpose, effect on live traffic, and access requirements. The notable remaining gap is whether supplying one field leaves the others untouched (partial update 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 60%, with title and target_url undocumented in the schema; the description partly compensates by naming the fields that can be modified, but it adds no format or constraint detail (URL validation, title length) beyond what the schema implies. 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?

States a specific verb plus the resource and the exact mutable fields ('Change the target URL (or title, or pause/activate) of an existing code'). The word 'existing' distinguishes it from create_qr_code without needing to name the sibling.

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?

Gives a clear condition for use — an already-created code whose destination or state should change — and states the prerequisite ('Needs the API key of the owner or the edit_url of an anonymous code'). It does not explicitly exclude alternatives such as creating a new code instead, so it falls short of a 5.

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.