Skip to main content
Glama

QRavate QR codes

Créer un QR code dynamique

create_qr_code

Crée un QR code dynamique vers une URL, avec un design (style, couleurs, icône ou logo au centre, texte d’appel). La destination reste modifiable après impression, et les scans sont comptés. 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": {
      "name": "<name>",
      "destination": "<destination>"
    },
    "name": "create_qr_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesNom pour s’y retrouver, par exemple « Menu terrasse ».
designNoApparence du QR code. Tout est facultatif : sans design, le code est noir sur blanc.
destinationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare the write/mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the description's job is to add context — and it does, disclosing that the destination remains editable after printing, that scans are tracked, and that write access is required. It does not describe the returned artifact, but the auth requirement and post-creation mutability are the material behavioral facts here.

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: capability first, then the dynamic-behaviour differentiators, then the access prerequisite — nothing wasted and no repetition of the schema. The parenthetical design list is slightly long but earns its place by previewing the nested object.

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 creation tool with no output schema and a nested design object, the description covers what is created, how it behaves afterwards, and the access requirement. It stops short of saying what the call returns (image, URL, id) or what happens on duplicate names, which is the only remaining gap.

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?

Schema coverage is 67% and the bare "destination" URI parameter carries no schema description, but the description frames it as the URL the code points to. It also summarizes the nested design object (style, colours, central icon or logo, call-to-action text), giving an agent a mental model before parsing the many enum fields.

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?

"Crée un QR code dynamique vers une URL" states a specific verb, resource and variant, which implicitly separates it from create_static_qr_code. An agent can tell what it produces and what makes it dynamic (editable destination, counted scans) 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description supplies the deciding context for a dynamic code (destination stays modifiable after printing, scans are counted) and a precondition ("Nécessite l'accès en écriture"). However it never explicitly routes the agent to or away from the sibling create_static_qr_code or update_qr_design, so the choice is left to inference from the word "dynamique".

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