Skip to main content
Glama

imprent.es - catálogo y precios de impresión

Coste de envío / Shipping cost

envio
Read-onlyIdempotent

Coste de envío (sin IVA y con IVA) de un producto y cantidad a un código postal español, con la misma lógica que el pago. No enviamos a Canarias, Ceuta ni Melilla. / Shipping cost for a product and quantity to a Spanish postal code, same logic as checkout. We do not ship to the Canary Islands, Ceuta or Melilla.

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": {
      "slug": "<slug>",
      "cantidad": "<cantidad>",
      "cp": "<cp>"
    },
    "name": "envio"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpYesCódigo postal de entrega (5 dígitos) / Delivery postal code.
slugYesSlug del producto (de buscar_productos) / Product slug (from buscar_productos).
cantidadYesUnidades / Units.
opcionesNoOpciones del producto (las que devuelve detalle_producto; las que falten usan el valor por defecto) / Product options (omitted ones use the default).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / cantidad / description
      Added value: +"Unidades / Units."
    • addedInput schema / properties / opciones / properties / acabado / description
      Added value: +"Valor de «acabado» tal como lo devuelve detalle_producto / Value of \"acabado\" as returned by detalle_producto."
    • addedInput schema / properties / opciones / properties / caras / description
      Added value: +"Valor de «caras» tal como lo devuelve detalle_producto / Value of \"caras\" as returned by detalle_producto."
    • addedInput schema / properties / opciones / properties / esquinas / description
      Added value: +"Valor de «esquinas» tal como lo devuelve detalle_producto / Value of \"esquinas\" as returned by detalle_producto."
    • addedInput schema / properties / opciones / properties / formato / description
      Added value: +"Valor de «formato» tal como lo devuelve detalle_producto / Value of \"formato\" as returned by detalle_producto."
    • addedInput schema / properties / opciones / properties / papel / description
      Added value: +"Valor de «papel» tal como lo devuelve detalle_producto / Value of \"papel\" as returned by detalle_producto."
    • addedInput schema / properties / slug / description
      Added value: +"Slug del producto (de buscar_productos) / Product slug (from buscar_productos)."
  2. First observed

TDQS

A4/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 the safety profile is covered. The description adds genuine context beyond that: the result includes both pre-tax and post-tax amounts, and the checkout parity implies this is an authoritative quote rather than an estimate.

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

Conciseness5/5

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

Two sentences in each language, with the computed value first and the geographic exclusion second. Every clause carries information an agent needs; the bilingual duplication is functional, not padding.

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 read-only pricing tool with no output schema, the description tells the agent what comes back (cost with and without VAT) and which inputs are unsupported. The main residual gap is that required product options from detalle_producto are only explained in the schema, not in the description.

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%, including the nested opciones fields tied to detalle_producto, so the schema carries the parameter burden. The description only reiterates product, quantity and postal code already documented, adding no format, default or edge-case semantics of its own.

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?

States a specific computed value (shipping cost with and without VAT) for a specific input triple (product, quantity, Spanish postal code), which unambiguously separates it from siblings like precio or detalle_producto. It stops short of naming an alternative, so differentiation is inferred rather than stated.

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?

Gives a hard when-not constraint — no shipping to the Canary Islands, Ceuta or Melilla — which is real routing guidance an agent needs before calling. It also anchors the calculation to 'the same logic as checkout', but never says which sibling to call first or what to do instead when the postal code is excluded.

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