QR for Agent

delete_qr_code

Permanently delete a QR code and all its scan analytics. The short URL stops working immediately. This action cannot be undone.

Instructions

Permanently delete a QR code and all its scan analytics. The short URL will stop working immediately. This cannot be undone.

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": {
      "short_id": "<short_id>"
    },
    "name": "delete_qr_code"
  }
}

Input Schema

Name	Required	Description	Default
`short_id`	Yes	The short ID of the QR code to delete.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Mar 30, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Discloses that deletion is permanent, analytics are removed, and the URL stops working. With no annotations, this adds sufficient behavioral context beyond the schema.

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?

Two sentences, no wasted words. Front-loaded with action and consequences.

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 simple delete tool without output schema, the description covers what the agent needs to know: irreversible action, and affected resources.

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 covers the single parameter 'short_id' with a description. The tool description adds no additional meaning beyond what the schema provides, meeting baseline for high coverage.

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?

The description clearly states 'delete a QR code' and specifies the scope ('and all its scan analytics'). It differentiates from siblings like bulk_delete_qr_codes by focusing on single deletion.

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?

The description warns about permanence and immediate effect, implying irreversible action. It does not explicitly mention when to use vs alternatives like bulk_delete, but the guidance is clear enough for a deletion tool.

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