Skip to main content
Glama

create_checkout

Créer un lien de paiement Stripe sécurisé pour un panier d'articles Cadorama. Deux modes : livraison à domicile en France métropolitaine (frais de port INCLUS, calculés par la boutique) ou retrait GRATUIT au magasin de Saint-Quentin (delivery: "retrait"). La réponse chiffre aussi le Point Relais, souvent moins cher, qui se choisit sur le site : avant de transmettre le lien, signale à l'utilisateur toute option moins chère. Produits réservés aux majeurs (alcool, tabac…), produits frais ou surgelés en précommande et produits à variantes exclus : les commander sur https://www.cadorama02.fr. Retourne une URL que l'utilisateur doit ouvrir pour payer (carte bancaire) ; la commande est créée automatiquement après paiement.

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": {
      "items": "<items>"
    },
    "name": "create_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesListe des articles à commander
deliveryNo« domicile » (défaut) : livraison Colissimo en France métropolitaine ; « retrait » : retrait gratuit au magasin, 119 rue d'Isle, 02100 Saint-Quentin (aucune adresse demandée)
customerEmailNoEmail du client pour la confirmation de commande (optionnel)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / customerEmail / pattern
      Added value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
    • removedInput schema / properties / items / items / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond annotations, the description discloses crucial behavior: the tool returns a URL the user must open to pay, the order is only created after payment, shipping is included for home delivery, the response also prices Point Relais, and the agent should flag cheaper options to the user. These details materially improve safe and correct invocation, with no contradiction of 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first sentence, followed by conditional details about delivery, cheaper alternatives, and excluded products. It is dense but every sentence carries relevant operational context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given there is no output schema and full parameter-schema coverage, the description supplies the missing operational context: return value (URL), post-payment order creation, payment method, delivery modes, product exclusions, and the cheaper Point Relais warning. An agent has enough information to invoke and explain the tool correctly.

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?

Schema description coverage is 100%, so the baseline is 3. The description repeats the delivery-mode semantics already documented in the schema and adds little about 'items' or 'customerEmail' beyond what the schema provides.

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?

The first sentence states a specific verb and resource: 'Créer un lien de paiement Stripe sécurisé pour un panier d'articles Cadorama'. It is clearly the only creation-oriented sibling among read/payment-check tools, but the description does not explicitly differentiate itself from alternatives such as check_payment.

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 clearly explains the two delivery modes and when to use each ('domicile' vs 'retrait'), and lists product exclusions with the alternative website for those cases. It does not, however, route the agent to or away from sibling tools such as check_payment or search_products.

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