Spočítá cenu nakonfigurovaného trička (vč. DPH) — podle množství/velikostí, počtu potištěných stran a promo kódu.
| Name | Required | Description | Default |
|---|---|---|---|
| sizes | No | mapování velikost→počet, např. {"M":10,"L":5} | |
| product | Yes | ||
| quantity | No | ||
| promoCode | No | ||
| printedSides | No | počet potištěných stran 0–4 | |
| printSideHeightsCm | No | výška motivu v cm na každé potištěné straně |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds that the price includes VAT, which is useful behavioral context, but it does not disclose return format, error cases, or any other operational details.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence, front-loaded with the verb and purpose, with no redundant information. It efficiently conveys the core behavior.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description should ideally convey what the tool returns, but it only states the pricing function. Given the read-only annotation and clear purpose, it is minimally complete, but the omission of printSideHeightsCm and the required product parameter leaves gaps for an agent trying to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is only 50%, and the description should compensate for undocumented parameters. It mentions quantity/sizes, printed sides, and promo code, but omits the required product parameter and printSideHeightsCm. For the parameters it does mention, it adds little beyond the schema, leaving key semantics unexplained.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool calculates the price of a configured T-shirt including VAT, distinguishing it from siblings like create_order or get_order_status. The verb 'Spočítá' (calculates) and resource 'cenu nakonfigurovaného trička' are specific and unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context for when to use the tool: when pricing a configured T-shirt before placing an order. It does not explicitly state exclusions or alternatives, but the sibling tool names and the read-only nature make the intended usage obvious.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource or workflow step: product catalog (list_products), price estimation (get_quote), design creation (create_design), order placement (create_order), and status tracking (get_order_status). The pricing overlap between create_design and get_quote is resolved by clear descriptions: one validates and saves a design with an estimated print cost, the other calculates a full shirt quote independently.
All tool names follow a consistent verb_noun pattern: create_ for creation, get_ for retrieval, and list_ for listing. There are no mixed conventions or vague verbs, making the naming predictable and easy to navigate.
Five tools is well-sized for the server's purpose as a custom apparel configurator. It covers the essential steps—product browsing, quoting, design, ordering, and status—without redundancy or unnecessary bulk.
The tools provide a complete ordering flow: discover products, get a quote, create a design, place an order, and check status. Minor gaps exist, such as no design management (list/update/delete) or order cancellation, but these are not critical to the core configuration and ordering workflow.
