Skip to main content
Glama

Motif & Moi

Lancer une commande de groupe

create_group_order

Pour un club, une classe, une association : crée le modèle et deux liens. Le lien membres est à partager (WhatsApp, e-mail) : chacun y choisit sa taille, saisit son prénom et son numéro si le modèle en a (texte per_piece), et paie sa part en ligne si pay_mode vaut members. Le lien responsable est privé : il suit les inscriptions et passe la commande pour tous à la date limite (il vérifie alors le visuel et paie le solde). Plus le groupe est nombreux, moins c’est cher : la remise porte sur tout le groupe et le trop-perçu des premiers inscrits leur est remboursé.

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": {
      "category": "<category>",
      "title": "<title>"
    },
    "name": "create_group_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorNoCouleur du vêtement (nom de list_products, ex. Noir).
textsNoTextes imprimés. Pour un prénom ou un numéro différent sur chaque pièce : per_piece, sans text, et la liste pieces.
titleYesNom de la commande, ex. « Sweats du FC Rennes Sud ».
qualityNoQualité : eco, standard (défaut) ou premium, selon la catégorie.
categoryYesCatégorie (identifiant de list_products), ex. t-shirt, sweat, hoodie, polo, tote-bag.
deadlineNoDate limite des inscriptions (AAAA-MM-JJ), à venir.
logo_urlNoAdresse https publique du logo (PNG, JPG, WebP ou SVG, 10 Mo max).
pay_modeNomembers (défaut) : chacun paie sa part en ligne ; owner : le responsable règle tout.
logo_sizeNoTaille dans la zone : s (petit), m (moyen, défaut), l (grand).
logo_sidesNoFaces qui portent le logo (défaut : front).
logo_base64NoLogo encodé en base64 (à la place de logo_url).
front_formatNoDevant : petit logo sur le cœur (compris dans le prix) ou grand format (supplément).
logo_filenameNo
club_margin_pctNoAvec pay_mode members : marge en % ajoutée au prix de chaque membre pour la caisse du club, reversée au club par virement après la commande (IBAN à saisir sur owner_url).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / logo_url / description
      Previous value: -"Adresse https publique du logo (PNG, JPG, WebP ou SVG, 20 Mo max)."New value: +"Adresse https publique du logo (PNG, JPG, WebP ou SVG, 10 Mo max)."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (non-readonly, non-idempotent, open world), the description discloses the actual side effects: two links are generated, one public for members and one private for the owner, payments are collected at signup, the owner closes the order at the deadline, and tiered pricing triggers refunds of overpayment. That is material behavior an agent could not infer from the hints.

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?

The audience and the created artifacts are front-loaded in the first clause, and the following sentences each explain a distinct part of the flow. It is dense and runs long as a single block, but no sentence is filler.

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 14-parameter creation tool with no output schema, the description covers the workflow, payment responsibility, and pricing consequences well. It could state what the response returns (the member and owner links) since there is no output schema to document that.

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 already 93%, so the baseline is 3, but the description adds real cross-parameter meaning: per_piece is explained as the variable name/number path that replaces static text, and pay_mode's effect on who pays is spelled out. It does not cover club_margin_pct's payout mechanics beyond the schema's own wording.

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?

States a specific verb and resource ('crée le modèle et deux liens') scoped to clubs, classes and associations, which immediately separates it from get_group_status and get_order_status (follow-up reads) and from create_design (single-piece design). An agent can tell what the tool produces 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 Guidelines4/5

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

The framing 'Pour un club, une classe, une association' gives a clear condition for selecting this tool over a single-order path, and the two-link flow clarifies the intended lifecycle. It stops short of explicitly naming alternatives such as create_design or get_quote or stating when not to use it.

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