Skip to main content
Glama

QRavate QR codes

Règles de redirection

set_redirect_rules
DestructiveIdempotent

Remplace les règles de redirection d’un QR code (liste ordonnée : la première règle active dont toutes les conditions sont remplies l’emporte ; sinon, destination principale). Conditions : device, os, app, lang, country, weekday (1 = lundi), time { from, to } en HH:MM, date { from, to } en AAAA-MM-JJ. Plusieurs destinations avec weight (somme 100) font un test A/B. Plans Pro et Max. Une liste vide retire les règles. 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>",
      "rules": "<rules>"
    },
    "name": "set_redirect_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
qrYes
clockNo
rulesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, and the description reinforces rather than contradicts them: 'Remplace' signals existing rules are overwritten, and the empty-list note makes full removal explicit. It adds real behavioral context beyond annotations — first-match-wins evaluation order, A/B behavior when multiple weighted destinations sum to 100, plan gating, and the write-permission requirement.

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?

A single dense paragraph with zero filler, front-loading purpose before semantics and ending with plan/permission constraints. It is efficient but very tightly packed; splitting the condition vocabulary from the behavioral rules would scan faster.

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 destructive, nested-schema mutation with no output schema, the description supplies nearly everything an agent needs — ordering semantics, per-condition meaning, A/B weighting, empty-list removal, and access requirements. The remaining gap is the unmentioned 'clock' selector and item limits, which an agent would only discover from the raw schema.

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?

With 0% schema description coverage, the description does heavy lifting: it enumerates every condition key (device, os, app, lang, country, weekday, time, date), explains weekday 1 = Monday, and specifies HH:MM and YYYY-MM-DD formats plus weight-summing-to-100 for A/B. It omits the top-level 'clock' enum (paris/scanner) and the rule 'name'/'active' fields and item caps, so the nested payload is not fully covered.

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 and resource — 'Remplace les règles de redirection d'un QR code' — and immediately clarifies the object is an ordered rule set, not a single destination, which separates it from update_destination or schedule_destination_change. The match-resolution rule (first active rule with all conditions met wins, else primary destination) further pins down what the tool actually changes.

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?

It gives clear triggering context (replacing a QR code's routing logic, Pro/Max plan, write access required) and explicitly documents the removal case: an empty list removes the rules. It does not, however, name an alternative such as update_destination for a single catch-all redirect, so an agent must infer when a rule set is overkill.

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