Skip to main content
Glama

QRavate QR codes

Créer un QR code statique

create_static_qr_code
Read-onlyIdempotent

Crée un QR code statique (Wi-Fi, texte, e-mail, téléphone, SMS, vCard ou URL figée). Il ne se modifie pas après impression et ne compte pas les scans : pour un lien qu’on voudra changer ou mesurer, préférez create_qr_code. Les données ne sont pas conservées par QRavate.

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": {
      "type": "<type>"
    },
    "name": "create_static_qr_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNotype url : adresse.
bodyNo
ssidNotype wifi : nom du réseau.
textNotype text : texte.
typeYes
emailNotype email : destinataire.
phoneNotypes tel et sms : numéro.
titleNo
designNoApparence du QR code. Tout est facultatif : sans design, le code est noir sur blanc.
addressNo
messageNotype sms : message.
subjectNo
websiteNo
lastNameNo
passwordNotype wifi : mot de passe.
securityNo
firstNameNotype vcard.
organizationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The description adds real behavior beyond the annotations: immutability after printing, no scan analytics, and the fact that QRavate does not retain the encoded data — which also explains why readOnlyHint=true is coherent for a tool whose name says 'create'. It does not tell the agent what the call returns (an image, a downloadable file, a payload), which is the remaining gap. No contradiction with the annotations.

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, front-loaded with what the tool produces, then the immutability caveat and the routing hint, then the data-retention note. No filler and nothing buried.

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 complex 18-param generator with a nested design object and no output schema, the definition covers purpose, alternative routing and the key behavioral caveats, which is enough to select the tool confidently. It stops short of helping the agent construct a valid call (which fields are required per type, what the response contains).

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?

With 18 parameters, a nested design object and only 50% schema description coverage, the schema does most of the work and the description adds meaning only implicitly, via the list of payload types that indicates which data fields (ssid/password, email/subject, phone/message, vcard names) apply per type. It never mentions the required type parameter, the design object, or how conditional fields pair up.

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 opens with a specific verb (Crée) and resource (QR code statique) and enumerates the supported payload types (Wi-Fi, texte, e-mail, téléphone, SMS, vCard, URL figée), which maps directly onto the type enum. It also explicitly marks itself as the static, non-editable variant, making it distinguishable from create_qr_code without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It states the two decisive constraints (not modifiable after printing, does not count scans) and then names the alternative: use create_qr_code for a link that must be changed or measured. That is an explicit when-to-use / when-not-to-use pairing with the sibling named.

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