Skip to main content
Glama

Make My QR Codes

Change a code

update_code
DestructiveIdempotent

Change where a printed website-link code points, a contact card's details, a code's name or folder, or pause and resume a changeable code. Changing the destination affects everyone who scans it from then on, so confirm with the person first. Codes can't be deleted here.

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_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe code: its id from list_codes, or a changeable code's link ending (e.g. "menu" for makemyqrcodes.com/menu)
nameNo
folderNo
statusNoPaused codes show a "paused" page when scanned
contactNoContact cards: the full new card (replaces the old one)
destinationNoWebsite-link codes: the new web address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the fundamental risk profile is known. The description adds real value beyond that: it warns that changing the destination affects every future scan, and clarifies that codes cannot be deleted here, which prevents an agent from attempting a removal.

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 primary action, followed by the risk warning and the deletion exclusion. No redundant restatement of the title.

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?

For a six-parameter mutation with a nested contact object and no output schema, the description covers the important mutation semantics well. It omits what happens when a non-changeable (static) code is passed, and says nothing about the result of the update, leaving modest gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema covers 67% of parameters, including enum and nested contact fields. The description adds type-conditional meaning by grouping mutations by code kind (website-link destination, contact card replacement, name/folder, pause/resume), helping the agent pick the right field for the code at hand.

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?

The description opens with a specific verb and resource ('Change where a printed website-link code points...') and enumerates the mutable facets: destination, contact card, name, folder, and pause/resume status. It's clear what it does, though it doesn't explicitly name siblings like create_code or get_code for contrast.

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?

It gives a meaningful caution ('confirm with the person first') and an exclusion ('Codes can't be deleted here'), which implies this is the only mutation path. However, it never states when to reach for this versus create_code or get_code, so the agent must infer the boundary.

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.

Resources