Skip to main content
Glama
Sign In

Suorigo Konfigurátor

by cz.suorigo.konfigurator
OverviewDiscussionsAdmin

quote_order

Read-only

Přesná cena celé objednávky PŘED založením — stejný výpočet jako create_order (položky, doprava vč. dopravy zdarma od 1 500 Kč, kupón, termín výroby). Vrací totalVat, rozpis, dostupné termíny (deliverySpeeds), ceny dopravy a v requirements co ještě chybí k objednání. Nic neukládá.

Input Schema

NameRequiredDescriptionDefault
itemsYespoložky objednávky (každá velikost/barva zvlášť)
customerNovolitelné: email (kvůli limitu kupónu), name, ico, adresy — jen pro kontrolu requirements
promoCodeNoslevový kód; neplatný kód = chyba (nikdy tiše plná cena)
shippingIdNodoprava: zasilkovna (výdejní místo / Z-BOX, 89 Kč), balikovna (69 Kč), ppl-vydejni (69 Kč), dpd-vydejni (89 Kč), ppl (na adresu, 119 Kč), dpd (na adresu, 109 Kč); od 1 500 Kč zdarma
pickupPointIdNoid výdejního místa z find_pickup_points (povinné u dopravy na výdejní místo)
deliverySpeedIdNotermín: d14 = do 14 prac. dní (výchozí, bez příplatku), d7 = do 7 dní +30 % (jen trička Standard), d30 = do měsíce −10 %; nedostupný termín = 400 s důvodem (quote_order ukáže dostupnost)
pickupPointNameNonázev výdejního místa (volitelné, doplní se samo)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / shippingId / description
      Previous value: -"doprava: zasilkovna (výdejní místo / Z-BOX, 89 Kč), balikovna (69 Kč), ppl-vydejni (79 Kč), dpd-vydejni (89 Kč), ppl / dpd (na adresu, 129 Kč); od 1 500 Kč zdarma"New value: +"doprava: zasilkovna (výdejní místo / Z-BOX, 89 Kč), balikovna (69 Kč), ppl-vydejni (69 Kč), dpd-vydejni (89 Kč), ppl (na adresu, 119 Kč), dpd (na adresu, 109 Kč); od 1 500 Kč zdarma"
  2. Changed2 schema fields changed
    • changedInput schema / properties / shippingId / description
      Previous value: -"doprava: zasilkovna (výdejní místo / Z-BOX, 89 Kč), balikovna (69 Kč), ppl-vydejni (79 Kč), dpd-vydejni (89 Kč), ppl / dpd (na adresu, 129 Kč); od 1 500 Kč zdarma; osobni (Šitbořice) jen se slevovým kódem, který ho odemyká"New value: +"doprava: zasilkovna (výdejní místo / Z-BOX, 89 Kč), balikovna (69 Kč), ppl-vydejni (79 Kč), dpd-vydejni (89 Kč), ppl / dpd (na adresu, 129 Kč); od 1 500 Kč zdarma"
    • changedInput schema / properties / shippingId / enum
      Previous value: -[
-  "zasilkovna",
-  "balikovna",
-  "ppl-vydejni",
-  "dpd-vydejni",
-  "ppl",
-  "dpd",
-  "osobni"
-]New value: +[
+  "zasilkovna",
+  "balikovna",
+  "ppl-vydejni",
+  "dpd-vydejni",
+  "ppl",
+  "dpd"
+]
  3. Changed3 schema fields changed
    • changedInput schema / properties / deliverySpeedId / description
      Previous value: -"termín: d14 = do 14 prac. dní (výchozí, bez příplatku), d7 = do 7 dní +30 % (jen trička Standard), rush3 = expres do 3 prac. dnů +100 % (jen černá/bílá trička Standart, objednávka 1 500–5 000 Kč, podání do 12:00), d30 = do měsíce −10 %; nedostupný termín = 400 s důvodem (quote_order ukáže dostupnost)"New value: +"termín: d14 = do 14 prac. dní (výchozí, bez příplatku), d7 = do 7 dní +30 % (jen trička Standard), d30 = do měsíce −10 %; nedostupný termín = 400 s důvodem (quote_order ukáže dostupnost)"
    • changedInput schema / properties / deliverySpeedId / enum
      Previous value: -[
-  "rush3",
-  "d7",
-  "d14",
-  "d30"
-]New value: +[
+  "d7",
+  "d14",
+  "d30"
+]
    • changedInput schema / properties / items / items / properties / colorName / description
      Previous value: -"název barvy (rozhoduje i o expresu: jen černá/bílá)"New value: +"název barvy"
  4. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'Nic neukládá'. It adds useful behavioral context beyond annotations by guaranteeing the quote uses the identical calculation as create_order and that `requirements` surfaces missing prerequisites, though it does not spell out error behavior (that lives in the schema).

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-loaded with the core purpose, then lists what it returns in a single dense paragraph with no filler. Slightly long, but every clause (free-shipping threshold, requirements output, no persistence) carries weight.

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?

No output schema exists, so the description carries the return-value burden and does so reasonably: totalVat, breakdown, deliverySpeeds, shipping prices, and `requirements`. Combined with annotations covering the safety profile, an agent has enough to call this correctly, though the nested `items` structure could use a bit more guidance.

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 items, customer, promoCode, shippingId, deliverySpeedId and pickupPointId in detail, including prices and enums. The description only restates the same input categories (items, shipping incl. free-shipping threshold, coupon, term) without adding syntax or format meaning, so the baseline 3 is appropriate.

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 ('Přesná cena celé objednávky PŘED založením') and explicitly ties itself to create_order ('stejný výpočet jako create_order') while disambiguating the safe-preview nature ('Nic neukládá'). An agent can distinguish this from the sibling create_order without opening the 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?

Clear context: use this to compute an order price before placing it, mirroring the create_order calculation and revealing what is missing via `requirements`. It does not, however, address the existence of the sibling get_quote or explain when this should be preferred over it, leaving one routing ambiguity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Suorigo Konfigurátor toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources