Skip to main content
Glama

Ortopedia Low Cost (Ortopedia Moliner — España)

Crear enlace firmado de carrito para checkout humano

create_checkout_cart_link

Crea un carrito invitado real en PrestaShop mediante el mismo motor central de cálculo fiscal que quote_configuration_and_delivery y devuelve una URL firmada HMAC con caducidad hacia OLC Smart Checkout. Nunca utiliza el IVA 4% del catálogo como sustituto de la decisión fiscal: si has_disability_certificate_33 es false u omitido, fuerza el IVA general estándar (active=0 en ps_orto_vat4_cart); solo aplica IVA 4% si has_disability_certificate_33=true tras confirmación expresa y validación de requisitos. No ejecuta cobro ni pedido sin acción humana.

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": {
      "product_id": "<product_id>"
    },
    "name": "create_checkout_cart_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
postcodeNoCódigo postal español de 5 dígitos para conciliar impuestos territoriales y transporte (por defecto toma customer_prefill.postcode o "46460").
quantityNoCantidad del producto principal (1 a 20, por defecto 1).
product_idYesID del producto principal a añadir al carrito.
accessory_idsNoIDs opcionales de accesorios compatibles a incluir en el mismo carrito.
combination_idNoID de la combinación/variante (0 si es simple o variante por defecto).
customer_prefillNoOpcional: datos facilitados expresamente por el comprador para pre-rellenar su formulario de entrega (no crea pedido ni ejecuta pago).
go_straight_to_checkoutNoSi es true (por defecto), abre directamente OLC Smart Checkout en 1 paso; si es false, lleva al resumen del carrito.
legal_requirements_confirmedNoConfirmación opcional expresa de cumplimiento de los requisitos legales del art. 91.Dos.1.4º Ley 37/1992 para aplicar IVA 4%.
has_disability_certificate_33NoDecisión fiscal expresa: false u omitido fuerza el IVA general estándar (10% o 21%, active=0 en ps_orto_vat4_cart); true aplica IVA reducido 4% únicamente tras confirmación expresa del comprador y validación de elegibilidad y territorio.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / has_disability_certificate_33 / description
      Previous value: -"Opcional: si es false explícitamente en un artículo elegible para IVA 4%, preconfigura el carrito en IVA general sin certificado."New value: +"Decisión fiscal expresa: false u omitido fuerza el IVA general estándar (10% o 21%, active=0 en ps_orto_vat4_cart); true aplica IVA reducido 4% únicamente tras confirmación expresa del comprador y validación de elegibilidad y territorio."
    • addedInput schema / properties / legal_requirements_confirmed
      Added value: +{
      +  "description": "Confirmación opcional expresa de cumplimiento de los requisitos legales del art. 91.Dos.1.4º Ley 37/1992 para aplicar IVA 4%.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / postcode
      Added value: +{
      +  "description": "Código postal español de 5 dígitos para conciliar impuestos territoriales y transporte (por defecto toma customer_prefill.postcode o \"46460\").",
      +  "type": "string"
      +}
  2. Changed6 schema fields changed
    • addedInput schema / properties / customer_prefill / properties / address1 / description
      Added value: +"Calle, número, piso y puerta de entrega."
    • addedInput schema / properties / customer_prefill / properties / city / description
      Added value: +"Población o localidad de entrega."
    • addedInput schema / properties / customer_prefill / properties / email / description
      Added value: +"Correo electrónico del comprador."
    • addedInput schema / properties / customer_prefill / properties / full_name / description
      Added value: +"Nombre y apellidos del destinatario."
    • addedInput schema / properties / customer_prefill / properties / phone / description
      Added value: +"Teléfono móvil de contacto de 9 dígitos."
    • addedInput schema / properties / customer_prefill / properties / postcode / description
      Added value: +"Código postal de 5 cifras en España."
  3. Changed4 schema fields changed
    • addedInput schema / properties / customer_prefill
      Added value: +{
      +  "description": "Opcional: datos facilitados expresamente por el comprador para pre-rellenar su formulario de entrega (no crea pedido ni ejecuta pago).",
      +  "properties": {
      +    "address1": {
      +      "type": "string"
      +    },
      +    "city": {
      +      "type": "string"
      +    },
      +    "email": {
      +      "type": "string"
      +    },
      +    "full_name": {
      +      "type": "string"
      +    },
      +    "phone": {
      +      "type": "string"
      +    },
      +    "postcode": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
    • changedInput schema / properties / go_straight_to_checkout / description
      Previous value: -"Si es true (por defecto), redirige directamente a la pantalla final de pago (/pedido); si es false, lleva al resumen del carrito."New value: +"Si es true (por defecto), abre directamente OLC Smart Checkout en 1 paso; si es false, lleva al resumen del carrito."
    • addedInput schema / properties / has_disability_certificate_33
      Added value: +{
      +  "description": "Opcional: si es false explícitamente en un artículo elegible para IVA 4%, preconfigura el carrito en IVA general sin certificado.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / quantity / description
      Previous value: -"Cantidad del producto principal (1 por defecto)."New value: +"Cantidad del producto principal (1 a 20, por defecto 1)."
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), and the description meaningfully extends this by disclosing that a real persisted guest cart is created, that the returned link is HMAC-signed with an expiry, and that no payment or order is executed. It could still warn that repeated calls create separate carts, but the added behavioral context is substantial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The core purpose is front-loaded in the first sentence, but the VAT 4% rule is explained twice in near-identical terms, inflating the text. It remains readable but contains redundancy that dilutes the otherwise strong opening.

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 nine-parameter tool with nested objects and no output schema, the description covers the important unknowns: the primary return value (signed URL with expiry) and the fiscal decision logic. Only minor gaps remain, such as the exact response payload shape and duplicate-cart behavior on repeated invocation.

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 coverage is 100%, so the schema already documents all nine parameters, including the nested customer_prefill fields. The description reinforces the fiscal meaning of has_disability_certificate_33 and legal_requirements_confirmed but largely restates what the schema and its property descriptions already say, so the baseline 3 applies.

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 states a precise verb+resource: it creates a real guest cart in PrestaShop and returns an HMAC-signed expiring URL to OLC Smart Checkout. It also distinguishes itself from the sibling quote_configuration_and_delivery by noting it uses the same fiscal engine but produces a checkout link rather than a quote.

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 establishes the operating context clearly (human checkout, no charge or order executed without human action) and names the sibling tool it shares logic with, letting an agent infer quote-vs-checkout routing. It stops short of an explicit 'use X instead when...' exclusion, so it is clear but not fully prescriptive.

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