Suorigo Konfigurátor

create_order

Idempotent

Založí ZÁVAZNOU objednávku (čeká na platbu) a vrátí platební instrukce: částku, číslo účtu, variabilní symbol, QR a odkaz na stav objednávky (statusUrl). Zákazníkovi zároveň odejde e-mail s platebními údaji. Platí člověk převodem — agent neplatí. Volej až po výslovném souhlasu zákazníka s položkami a cenou z get_quote. Vyžaduje skutečný e-mail zákazníka (doména musí přijímat poštu, jinak 422) a consent:true. Limity: 3 objednávky / IP / den, 2 nezaplacené na jeden e-mail; překročení = 429. Při opakování po timeoutu pošli stejný idempotencyKey — vrátí se tatáž objednávka místo duplicity.

Input Schema

TableJSON Schema

Name	Required	Description
`items`	Yes	položky: {product (id/slug), colorId?, colorName?, size, quantity, printMethod?, layers? (z create_design)}
`notes`	No	vzkaz zákazníka k objednávce (co má dílna vědět); uloží se k zakázce jako poznámka od zákazníka, delší text se ořízne
`consent`	Yes	souhlas s obchodními podmínkami, musí být true
`customer`	Yes	{email (povinné), name?, phone?, address?, companyName?, ico?, dic?, billingStreet?, billingCity?, billingZip?, billingCountry?}
`promoCode`	No
`shippingId`	No	např. 'zasilkovna','balikovna','ppl','dpd' (volitelné)
`idempotencyKey`	No	libovolný unikátní klíč této objednávky (např. UUID); opakované volání se stejným klíčem a obsahem vrátí stejnou objednávku (replayed:true), stejný klíč s jiným obsahem = 409

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 21, 2026

addedInput schema / properties / idempotencyKey

Added value: +{
+  "description": "libovolný unikátní klíč této objednávky (např. UUID); opakované volání se stejným klíčem a obsahem vrátí stejnou objednávku (replayed:true), stejný klíč s jiným obsahem = 409",
+  "maxLength": 128,
+  "type": "string"
+}

Changed2 schema fields changedAug 18, 2026

addedInput schema / properties / notes / description

Added value: +"vzkaz zákazníka k objednávce (co má dílna vědět); uloží se k zakázce jako poznámka od zákazníka, delší text se ořízne"

addedInput schema / properties / notes / maxLength
```
Added value: +1000
```

First observedJun 25, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Adds substantial behavior beyond annotations: sends email, returns payment instructions, states that the human pays by transfer and the agent must not pay, gives rate limits and 429 behavior, 422 for invalid email domains, and precise idempotency semantics including 409 for conflicting content. No contradiction with annotations.

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?

Description is dense and front-loaded with the core action and return value; every sentence carries distinct information. It is somewhat long as a single paragraph, but there is no filler.

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?

For a 7-parameter tool with nested objects and no output schema, the description covers return values, side effects, prerequisites, error conditions, rate limits, and idempotency behavior. The schema handles parameter details, and the description supplies enough operational context to invoke it correctly.

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 high at 86%, so the baseline is 3; description adds operational meaning beyond the schema by explaining consent must be true, email must accept mail, idempotencyKey retry behavior, and order limits. This is meaningful extra value.

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: creates a binding order awaiting payment and lists concrete outputs (amount, account number, variable symbol, QR, statusUrl). This clearly distinguishes it from siblings like get_quote or create_design.

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?

Explicitly says to call only after customer consent to items and price from get_quote, requires a real deliverable email and consent:true, and gives retry guidance with idempotencyKey. It does not explicitly name alternative tools for other steps, so it lacks full when-not guidance.

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 tools Inspect

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

Need Help?