Skip to main content
Glama

Ortopedia Low Cost (Ortopedia Moliner — España)

Calcular presupuesto exacto conciliado con IVA y envío

quote_configuration_and_delivery
Read-onlyIdempotent

Calcula el presupuesto exacto conciliado al céntimo contra el motor real Cart de PrestaShop de un equipo principal (con su variante/talla/batería) más accesorios opcionales. No asume automáticamente el IVA del 4%: aplica IVA estándar (10% o 21%) salvo que has_disability_certificate_33 sea true confirmado por el comprador, mostrando además la comparativa transparente con certificado, base imponible, cuota de IVA, descuento automático web (Tu Mejor Precio), transporte según código postal y ventana estimada de entrega.

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": "quote_configuration_and_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
postcodeNoCódigo postal español de 5 dígitos para cálculo exacto de impuestos territoriales y envío (por defecto "46460" Península).
quantityNoUnidades del producto principal (1 a 20, por defecto 1).
product_idYesID del producto principal en PrestaShop.
accessory_idsNoLista opcional de IDs de productos accesorios compatibles a añadir al conjunto.
combination_idNoID de la variante/combinación (0 para la predeterminada o producto simple).
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_33NoTrue únicamente cuando el comprador confirma expresamente que el destinatario dispone de certificado oficial de discapacidad >=33%, movilidad reducida o incapacidad permanente/dependencia en España (por defecto false si no se ha verificado; nunca asume el 4% por defecto).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / has_disability_certificate_33 / description
      Previous value: -"True únicamente cuando el comprador confirma que el destinatario dispone de certificado oficial de discapacidad >=33%, movilidad reducida o incapacidad permanente/dependencia en España (por defecto false si no se ha verificado)."New value: +"True únicamente cuando el comprador confirma expresamente que el destinatario dispone de certificado oficial de discapacidad >=33%, movilidad reducida o incapacidad permanente/dependencia en España (por defecto false si no se ha verificado; nunca asume el 4% por defecto)."
    • 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"
      +}
  2. Changed5 schema fields changed
    • changedInput schema / properties / accessory_ids / description
      Previous value: -"Lista opcional de IDs de productos accesorios compatibles a añadir al conjunto (ej. colchón, barandillas, maleta trasera)."New value: +"Lista opcional de IDs de productos accesorios compatibles a añadir al conjunto."
    • changedInput schema / properties / has_disability_certificate_33 / description
      Previous value: -"True si el destinatario dispone de certificado de discapacidad >=33%, movilidad reducida o incapacidad permanente para aplicar IVA 4% en productos elegibles."New value: +"True únicamente cuando el comprador confirma que el destinatario dispone de certificado oficial de discapacidad >=33%, movilidad reducida o incapacidad permanente/dependencia en España (por defecto false si no se ha verificado)."
    • addedInput schema / properties / postcode
      Added value: +{
      +  "description": "Código postal español de 5 dígitos para cálculo exacto de impuestos territoriales y envío (por defecto \"46460\" Península).",
      +  "type": "string"
      +}
    • changedInput schema / properties / product_id / description
      Previous value: -"ID del producto principal."New value: +"ID del producto principal en PrestaShop."
    • changedInput schema / properties / quantity / description
      Previous value: -"Unidades del producto principal (por defecto 1)."New value: +"Unidades del producto principal (1 a 20, por defecto 1)."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so behavioral burden is light. The description still adds real value: it will not default to the 4% VAT rate, it applies standard 10%/21% unless the certificate flag is explicitly confirmed, and it returns a transparent side-by-side comparison including shipping by postcode. It stops short of describing failure modes (e.g. invalid product_id or unsupported postcode).

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?

It is a single front-loaded sentence that states the core computation before the tax caveats, and no clause is filler. It is dense and run-on, however, so the tax-condition and shipping details would read better as a short follow-up rather than one continuous sentence.

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?

With 7 parameters, no output schema and full schema coverage, the description carries the remaining load well: it effectively enumerates the return contents (certificate comparison, base imponible, VAT amount, automatic web discount, shipping and delivery window). An agent has enough to know what it will get back and how the tax branch behaves.

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 100%, so the baseline is 3; the description earns above that by explaining the gating logic behind `has_disability_certificate_33` (4% only when the buyer explicitly confirms, never assumed) and by tying postcode to territorial tax and shipping calculation. It does not add semantics for `quantity`, `combination_id` or `legal_requirements_confirmed` beyond what the schema already says.

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 names a precise verb and object: computing an exact quote reconciled to the cent against PrestaShop's real `Cart` engine, covering a main product plus its variant/battery plus optional accessories. That scope is narrow enough to be unmistakably distinct from the catalog-search, clinical-sheet, policy-guide and checkout-link siblings.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the description makes clear this is the quoting step (it computes tax, shipping and delivery window), but it never explicitly says when to call it versus `create_checkout_cart_link` or `get_store_policies_and_vat4_guide`. The conditional VAT wording guides parameter choice, not tool selection.

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