Skip to main content
Glama

QRavate QR codes

Changer le design

update_qr_design
DestructiveIdempotent

Change l’apparence d’un QR code (style, couleurs, icône ou logo, texte d’appel). Le contenu encodé ne change pas : un code déjà imprimé reste valable. Nécessite l’accès en écriture.

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": {
      "qr": "<qr>",
      "design": "<design>"
    },
    "name": "update_qr_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
qrYes
designYesApparence du QR code. Tout est facultatif : sans design, le code est noir sur blanc.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and idempotentHint=true; the description adds genuinely useful context beyond them: the encoded content is untouched and an already-printed code stays valid, plus the write-access requirement. One notable gap remains: it does not say whether the supplied 'design' object merges with or replaces the existing design, which matters for a destructive-flagged update.

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, each carrying distinct information: what changes, what is preserved, what is required. Zero filler and the key reassurance about printed codes is front-loaded.

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 nested 12-property mutation tool with a destructive hint and no output schema, the description covers purpose, safety and auth but omits return behaviour (is a preview/rendered image returned?) and partial-update semantics. Adequate to start, insufficient to call with confidence on ambiguous cases.

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?

The description names the design categories (style, colours, icon/logo, frame text) which broadly map onto the nested 'design' object, and the schema itself richly documents most sub-properties. However the required 'qr' parameter is left undefined (identifier vs. short code vs. URL) and the merge/replace semantics of the design object are unaddressed.

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?

States a specific verb-and-resource pair ('Change l'apparence d'un QR code') and enumerates the design surfaces it touches (style, colours, icon/logo, call-to-action text). The clause 'Le contenu encodé ne change pas' implicitly separates it from destination/content tools like update_destination, though no sibling is named explicitly.

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?

Conveys context — restyle an existing code, requires write access — but offers no explicit when-to-use/when-not guidance and never points to alternatives such as list_design_options for discovering presets, icons or brand logos. The agent must infer that presets/icons should be looked up elsewhere first.

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