Pinflower — flowers in Prague

Price the order

pinflower_quote_order

Read-onlyIdempotent

Use this when the buyer has chosen what to order and you have the details: it prices the order exactly as the checkout will charge it — the bouquet(s), add-ons, the shop's launch discount or the buyer's promo code, the delivery fee — and checks the time, without creating anything. Takes: the bouquet(s) (bouquet_id from search; several bouquets of ONE florist with quantities in items); delivery or pickup; for delivery the street address with house number in Prague; the recipient's name and phone when someone else receives the flowers; the date and a time (one of the bouquet's offered times, or 'asap'); the buyer's name, e-mail and phone (+420…); an optional card message and note for the florist; the buyer's promo code if they have one. Above 10 000 Kč the buyer's billing address is required. Also on offer: address_mode 'ask_recipient' when the florist should agree the address with the recipient by phone — a surprise (the recipient's name and phone are then required); time 'agree_with_recipient' when the florist should agree the time with the recipient by phone (the recipient's name and phone are then required); recipient.care_reminder=true — the free (0 Kč) care reminder for the recipient, offered once when someone else receives the flowers; company details (IČO) for a purchase by a company. Returns the breakdown, the total, the terms link and an order_intent; it creates nothing. The total is valid for exactly these details.

Input Schema

TableJSON Schema

Name	Required	Description
`date`	Yes	'today', 'tomorrow' or YYYY-MM-DD.
`time`	Yes	HH:MM from the offered times, or 'asap', or 'agree_with_recipient' (the florist agrees the time with the recipient by phone; delivery only).
`unit`	No	Apartment, floor, company at the door.
`buyer`	Yes
`items`	No	Several bouquets from the SAME florist, with quantities.
`locale`	No
`address`	No	Delivery to a known address: street and house number in Prague.
`company`	No	Buying for a company — the invoice is issued to it.
`recipient`	No	Who receives the flowers, when it is someone else than the buyer — the courier calls them.
`bouquet_id`	No	One bouquet (shortcut for items with a single line).
`fulfilment`	No
`promo_code`	No	The buyer's promo code, if they have one — works for guests and signed-in buyers alike; the checkout checks it.
`address_mode`	No	ask_recipient = the courier/florist agrees the address with the recipient by phone (a surprise); no address needed, delivery priced at the whole-city rate.
`card_message`	No
`courier_note`	No	Bell name, entrance, gate code.
`florist_note`	No
`billing_address`	No	The buyer's billing address — required by Czech tax rules when the order is over 10 000 Kč (unless buying for a company).
`marketing_opt_in`	No	true = the buyer asked for news and offers.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`discount`	No
`goods_czk`	Yes
`next_step`	Yes
`terms_url`	Yes
`total_czk`	Yes
`delivery_fee_czk`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 11, 2026

addedInput schema / properties / recipient / properties / care_reminder

Added value: +{
+  "description": "«A little extra care», free (0 Kč), off unless the buyer wants it: after the delivery Pinflower texts the recipient once (the sender ordered a care reminder; STOP opts out), and 3 days later sends one care tip. Delivery only, for a named recipient (recipient.phone is where the texts go — whose number it is does not matter); the recipient's language is unknown, the texts are Czech.",
+  "type": "boolean"
+}

Changed2 schema fields changedOct 1, 2026

changedInput schema / properties / items / items / properties / bouquet_id / description

Previous value: -"From pinflower_search_bouquets / pinflower_get_bouquet."New value: +"A bouquet_id as search results and bouquet details show it."

changedInput schema / properties / marketing_opt_in / description

Previous value: -"Only true if the buyer asked for news and offers."New value: +"true = the buyer asked for news and offers."

Changed2 schema fields changedSep 27, 2026

changedInput schema / properties / recipient / description

Previous value: -"Who receives the flowers, when it is someone else than the buyer — the courier calls them; required when the address or the time is agreed with the recipient."New value: +"Who receives the flowers, when it is someone else than the buyer — the courier calls them."

changedInput schema / properties / time / description

Previous value: -"HH:MM from the offered times, 'asap', or 'agree_with_recipient' (the florist agrees the time with the recipient by phone; delivery only)."New value: +"HH:MM from the offered times, or 'asap', or 'agree_with_recipient' (the florist agrees the time with the recipient by phone; delivery only)."

First observedSep 25, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, but the description adds genuinely non-structured context: the returned order_intent, the terms link, and critically 'The total is valid for exactly these details'. It also explains the ask_recipient surprise flow and the free care_reminder behavior, none of which the annotations convey.

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?

It is a long, dense block, but it is front-loaded with the trigger condition and internally ordered with 'Takes:', 'Also on offer:' and 'Returns:' markers. A fair amount of the parameter text duplicates the schema, which dilutes an otherwise efficient layout.

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 an 18-parameter, deeply nested tool, the description covers the required inputs, the conditional rules (10 000 Kč billing threshold, recipient-required flows, one-florist constraint) and the output contract, with an output schema present to carry the return detail. Nothing an agent needs to call 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 coverage is 72% and the description's parameter prose ('bouquet_id from search', 'several bouquets of ONE florist', 'billing address above 10 000 Kč', address_mode) largely restates what the schema descriptions already say. It frames the required set usefully but adds little syntax or format meaning beyond the structured fields.

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?

The description states a specific verb and resource ('it prices the order exactly as the checkout will charge it') and explicitly distinguishes itself from the write path with 'without creating anything' / 'it creates nothing'. An agent can tell it apart from pinflower_create_order and pinflower_cancel_order without opening a 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?

It gives a clear trigger: 'Use this when the buyer has chosen what to order and you have the details', and the repeated 'creates nothing' clause implicitly routes the agent to create_order for the actual purchase. However, it never names the alternative tool explicitly, so the exclusion is left to inference.

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

All Pinflower — flowers in Prague 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?