QR Code Dinosaur

Change where a QR code points

update_destination

DestructiveIdempotent

Pro only ($9/month), and needs an API key whose owner has Pro and owns the code. Points a "redirect" QR code at a new URL without reprinting it. Without a key, tell your user they can do this on QRCodeDinosaur.com after claiming the code and subscribing (see start_pro_subscription).

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": {
      "id": "<id>",
      "url": "<url>"
    },
    "name": "update_destination"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	QR code ID, e.g. "QR-ABCD1234EF". Must be a "redirect" code to have any effect on scans.
`url`	Yes	The new destination, an http or https URL.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare mutation (readOnlyHint=false, destructiveHint=true, idempotentHint=true), so safety is covered structurally. The description adds genuinely non-structured context: a paywall, an ownership auth requirement, and the fact that the printed code keeps working while its target changes. It does not spell out that the previous destination is overwritten, which would have fully justified the destructive hint.

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?

Three sentences, no filler, and the cost/auth gating is placed early where an agent will see it. The parenthetical pricing and prose-style fallback sentence could be tightened slightly, but nothing is redundant.

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 two-parameter mutation with no output schema, the essentials are present: who can call it, what it changes, what happens to existing printed codes, and the no-credentials path. Only the fate of the prior destination URL is left implicit.

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%, so both id and url are already documented including format examples and the redirect-code constraint. The description adds the purpose of the swap ('new URL', 'without reprinting') but no format or validation detail beyond the schema, which is the baseline expectation.

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 — 'Points a "redirect" QR code at a new URL' — plus the distinguishing benefit ('without reprinting it'). An agent can tell this apart from create_qr_code or get_scan_analytics without opening the schema.

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 precondition (Pro plan, API key whose owner holds Pro and owns the code) and an explicit fallback path when no key is available: tell the user to do it on QRCodeDinosaur.com and see start_pro_subscription. It stops short of naming a different tool to use for non-redirect codes, but the routing guidance present is concrete.

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

All QR Code Dinosaur tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?