Pinflower — flowers in Prague

Find bouquets

pinflower_search_bouquets

Read-onlyIdempotent

Use this when the buyer wants flowers delivered in Prague (or picked up there) and you need concrete bouquets: it returns only bouquets that can really arrive at the given place and time, with price, delivery fee, total and the earliest delivery time, in the storefront's recommended order. Takes what the buyer said: free text, occasion, budget, where, date and a deliver-by time; without date and deliver_by every result carries its earliest time. Each call displays its results to the buyer as a carousel. Not for general flower advice or for orders outside Prague.

Input Schema

TableJSON Schema

Name	Required	Description
`date`	No	Delivery/pickup day: 'today', 'tomorrow' or YYYY-MM-DD (Prague). Omit for as soon as possible.
`sort`	No	recommended (default, the storefront's order), cheapest, most expensive, or soonest arrival.
`limit`	No	How many results (default 6).
`query`	No	Free text in any language: flower, colour or bouquet name, e.g. 'red roses', 'tulipány', 'пионы'.
`style`	No	as_pictured = looks like the photo; florists_style = composed fresh by the florist in that spirit.
`where`	No	Where the flowers go, as the buyer said it: a Prague district ('Praha 5'), a quarter ('Vinohrady', 'Smíchov') or a street address. Omit when unknown.
`detail`	No	full adds composition and a short description (default short).
`locale`	No	The buyer's language for names, texts and links: cs, en, ru or uk (default cs).
`category`	No	A category slug as results show it (e.g. roses, tulips).
`currency`	No	Add an approximate EUR/USD preview for a buyer abroad (default czk). The charge is always in CZK.
`occasion`	No	The occasion the buyer named.
`ready_now`	No	Only bouquets already made and waiting (fastest).
`deliver_by`	No	HH:MM (24 h): must arrive by then. Without date it means today.
`fulfilment`	No	delivery (default) or pickup at the florist's shop.
`free_delivery`	No	Only bouquets whose delivery can be free: free for the address's zone when a place is given; before one, bouquets with a free path at some zone (the result's free_delivery says whether it IS free).
`budget_max_czk`	No	Bouquet price limit in CZK (delivery not included).
`budget_min_czk`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`empty`	No
`results`	Yes
`currency`	No
`interpreted`	Yes
`total_found`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 15, 2026

changedInput schema / properties / free_delivery / description

Previous value: -"Only bouquets with free delivery."New value: +"Only bouquets whose delivery can be free: free for the address's zone when a place is given; before one, bouquets with a free path at some zone (the result's free_delivery says whether it IS free)."

addedOutput schema / properties / results / items / properties / delivery_fee_exact

Added value: +{
+  "description": "The fee is the address's zone price; false = a 'from' lower bound until an address is known.",
+  "type": "boolean"
+}

addedOutput schema / properties / results / items / properties / time_exact

Added value: +{
+  "description": "The times are for the address; false = an estimate for a district's centre (a street address confirms them).",
+  "type": "boolean"
+}

Changed1 schema field changedOct 1, 2026

changedInput schema / properties / occasion / description

Previous value: -"Only when the buyer named the occasion. Never assume 'sympathy'."New value: +"The occasion the buyer named."

Changed1 schema field changedOct 1, 2026
- changedOutput schema / properties / results / items / properties / earliest / properties / day / enum
```
Previous value: -[
-  "today",
-  "tomorrow",
-  "later"
-]New value: +[
+  "today",
+  "tonight",
+  "tomorrow",
+  "later"
+]
```
First observedSep 25, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds real behavioral context the annotations cannot: every call renders its results to the buyer as a carousel, results are in the storefront's recommended order, and date/deliver_by omission changes the returned timing semantics. Return-value detail matters less because an output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the triggering condition ('Use this when...'), followed by return shape, input framing and the exclusion, in roughly four dense sentences with no filler. Every sentence carries distinct information—nothing restates the title or schema.

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?

For a 17-parameter, no-required-parameter tool, it covers role, output shape, the carousel side effect, and scope limits, and an output schema handles return structure. It leaves minor gaps such as how limit/sort interact and default result count, which the schema states but the narrative never hints at.

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 94%, so the baseline is 3, but the description adds meaning beyond the schema by framing the key inputs as 'what the buyer said' (free text, occasion, budget, where, date, deliver-by), which tells the agent these accept raw conversational phrasing rather than normalized values.

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+resource (search bouquets delivered in Prague) and precisely what the call returns: only bouquets that can arrive at the given place and time, with price, delivery fee, total and earliest delivery time. It also disambiguates from siblings like pinflower_check_delivery and pinflower_get_bouquet by tying itself to concrete purchasable bouquets rather than feasibility checks or single-bouquet lookup.

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 when-to-use ('buyer wants flowers delivered in Prague ... and you need concrete bouquets') and explicit when-not ('Not for general flower advice or for orders outside Prague'). It does not name a specific alternative sibling for those excluded cases, so it stops short of full routing guidance.

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?