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. Pass what the buyer said: free text, occasion, budget, where, date and a deliver-by time. Do not use it for general flower advice or for orders outside Prague. Show 3–6 results; then use pinflower_get_bouquet for details or pinflower_create_order to order.

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	Only when the buyer named the occasion. Never assume 'sympathy'.
`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 with free delivery.
`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.

First observedSep 25, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already mark the call as read-only and idempotent, and the description adds a concrete behavioral contract: only bouquets that can actually arrive at the given place/time, with price, delivery fee, total, earliest delivery time, and the storefront's recommended order. 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.

Conciseness5/5

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

The description is four purposeful, information-dense sentences with no filler. It front-loads the trigger condition and behavioral guarantee, then gives input guidance, exclusions, and next steps efficiently.

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?

Despite 17 parameters, the description plus 94% schema coverage and an output schema cover the full calling context: when to use it, what to pass, what results contain, and what to do next. Nothing essential for selecting and invoking the tool is missing.

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 schema already documents the parameters well. The description adds useful guidance by telling the agent to pass the buyer's own words for free text, occasion, budget, where, date, and deliver-by time, plus an explicit result-count expectation of 3–6.

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 action — returning concrete, deliverable bouquets — and scopes it to Prague delivery/pickup. It clearly distinguishes the tool from general flower advice and from other tools like get_bouquet or store_info.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says when to use this tool (buyer wants flowers delivered/picked up in Prague and needs concrete bouquets) and when not to ('Do not use it for general flower advice or for orders outside Prague'). It also routes follow-up actions to pinflower_get_bouquet and pinflower_create_order.

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?