Skip to main content
Glama

Dipromotions — catálogo y presupuestos

Calcular un precio orientativo

calcular_precio
Read-only

Precio orientativo en euros sin IVA de un producto del catálogo a una cantidad: unitario sin personalizar, unitario con marcaje, totales y los tramos de precio publicados. Es el mismo cálculo que la tabla de precios de la ficha web. No crea ninguna solicitud ni avisa a nadie. Los portes ya van incluidos en el precio (shipping dice cuánto suman: no los sumes otra vez) y availability trae el stock por color y qué colores cubren la cantidad. El plazo de entrega y el importe definitivo, que depende del acabado y el color, se confirman en presupuesto.

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": {
      "masterCode": "<masterCode>",
      "quantity": "<quantity>"
    },
    "name": "calcular_precio"
  }
}

Input Schema

NameRequiredDescriptionDefault
quantityYesUnidades. El pedido mínimo es de 25.
positionsNoPosiciones de marcaje; por defecto 1.
masterCodeYesCódigo del producto, por ejemplo `MO2562`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnlyHint and openWorldHint, and the description reinforces this with 'No crea ninguna solicitud ni avisa a nadie', so there is no side-effect ambiguity. It adds genuinely useful behavioral context beyond the annotations: shipping is already baked into the price and must not be added again, and delivery time plus the definitive amount depend on finish and color and are only confirmed in a quote.

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?

Front-loads the purpose in the first clause and keeps every sentence earning its place — the shipping warning and the quote disclaimer both prevent real errors. The long opening sentence with nested parentheticals is dense but still readable; minor tightening would push it higher.

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 no output schema, the description carries the return-value burden and does so well: it names the unit prices, totals, tiers, plus the shipping and availability fields the caller will receive. For a 3-parameter read-only calculation tool, nothing an agent needs to call and interpret it correctly is missing.

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 schema already documents quantity (minimum 25), positions (default 1, max 10), and masterCode with an example. The description only hints at these via 'a una cantidad' and 'unitario con marcaje', adding no syntax or format detail beyond the schema, 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?

States a specific verb and resource (indicative price in euros ex-VAT for a catalog product at a given quantity) and enumerates the breakdown it returns: unit price unpersonalized, unit price with marking, totals, and published price tiers. It also distinguishes itself from the quoting sibling by declaring 'No crea ninguna solicitud ni avisa a nadie', so an agent can separate it from pedir_presupuesto without opening either schema.

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 clear context for use — it is the same calculation as the price table on the product page — and implicitly routes definitive pricing and delivery times to presupuesto. It does not name buscar_catalogo or pedir_presupuesto explicitly, nor state exclusions such as what to do if the masterCode is unknown, so the routing is clear but not fully spelled out.

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