Skip to main content
Glama

Manage recipient QR codes

spur_manage_qr_recipients
Destructive

Create one or up to 500 recipient codes under a redirect, update a code, or delete it. No outreach is sent. Edits/deletion affect printed codes.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is known. The description adds genuinely new context: no outreach is sent, and edits/deletion have downstream consequences on already-printed codes -- which is exactly the side-effect detail annotations cannot convey. It omits, however, that update/delete require an explicit user approval gate (only stated in the schema) and does not clarify whether deletion is recoverable.

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 short sentences, front-loaded with the capability set, with no filler. However, the final sentence 'Edits/deletion affect printed codes' is terse to the point of ambiguity -- an agent could read it as either 'printed codes break' or 'printed codes are unaffected'.

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 multi-action mutation tool with no output schema, the description covers the action set, side effects, and the printed-code caveat. It would be stronger if it flagged the mandatory confirm gate on update/delete and the irreversibility of deletion, but the schema already carries the confirm constraint at full coverage.

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 per-action fields, the required confirm flag with its explicit-approval wording, and the maxItems=500 cap are already documented in the schema. The description's 'up to 500' merely restates the schema bound and adds no new meaning about recipient fields, changes payload, or code_id semantics. Baseline 3 applies.

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 states specific verbs and resource: create one or bulk (up to 500) recipient codes under a redirect, update a code, or delete it. 'Recipient codes under a redirect' distinguishes this from redirect-level management (spur_manage_qr_redirect) and from generic code tools. It stops short of explicitly naming which sibling to use for single-code lifecycle operations versus this recipient-scoped tool.

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?

Usage is implied by the verb set -- create/update/delete recipient codes under a redirect -- but there is no explicit when-to-use versus when-not guidance, and no alternative tools are named for overlapping operations (e.g. spur_create_qr_code, spur_delete_qr_code, spur_update_qr_code). An agent must infer the boundary from the word 'recipient'.

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