Skip to main content
Glama

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

Precio de un presupuesto / Price quote

precio
Read-onlyIdempotent

Precio exacto con y sin IVA para un producto, cantidad, velocidad y opciones: el mismo que ve el cliente en la web. Incluye enlace a la ficha. / Exact price with and without VAT, the same one the customer sees on the website, with a link to the product page.

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>"
    },
    "name": "precio"
  }
}

Input Schema

NameRequiredDescriptionDefault
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).
velocidadNoClave de velocidad de detalle_producto (por defecto «estandar») / Speed key (default "estandar").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • 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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond them by disclosing what comes back: the exact customer-facing price split into with-VAT and without-VAT, plus a link to the product sheet. It does not mention currency or tax rate assumptions, which keeps it short of a 5.

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?

Two front-loaded sentences that put the price result first and the included link second; every clause carries information. The cost is duplicated Spanish/English text, which is defensible for a bilingual tool but adds length.

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 four-parameter read-only calculator with no output schema, the definition covers what matters: the price with and without VAT, that it matches the website, and that a product link is returned. Remaining gaps such as currency, applicable tax rate, and pricing tiers for large quantities are minor rather than blocking.

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 slug, cantidad, velocidad and the nested opciones are already fully documented, including that missing options fall back to defaults. The description merely restates the same parameter list (producto, cantidad, velocidad, opciones) without adding format or constraint detail, so the baseline of 3 applies.

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 verb and resource: computes the exact price with and without VAT for a product given quantity, speed and options, plus a link to the product page. It is clearly distinguishable from buscar_productos and detalle_producto by its pricing output, though it never names those siblings explicitly.

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 only implied: the mention of options and speed suggests it is called after detalle_producto, but the description states no when-to-use condition, no prerequisites, and no alternative to prefer. Guidance exists only indirectly through the schema's references to buscar_productos and detalle_producto.

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