Skip to main content
Glama

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pinflower_search_bouquets"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDelivery/pickup day: 'today', 'tomorrow' or YYYY-MM-DD (Prague). Omit for as soon as possible.
sortNorecommended (default, the storefront's order), cheapest, most expensive, or soonest arrival.
limitNoHow many results (default 6).
queryNoFree text in any language: flower, colour or bouquet name, e.g. 'red roses', 'tulipány', 'пионы'.
styleNoas_pictured = looks like the photo; florists_style = composed fresh by the florist in that spirit.
whereNoWhere 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.
detailNofull adds composition and a short description (default short).
localeNoThe buyer's language for names, texts and links: cs, en, ru or uk (default cs).
flowersNoPlant ids the bouquet must hold ANY of, as results show them under `flowers` (e.g. ["rosa"], ["rosa", "hydrangea"]). A plant covers its forms (spray roses are roses).
categoryNoA category slug as results show it (e.g. roses, tulips).
currencyNoAdd an approximate EUR/USD preview for a buyer abroad (default czk). The charge is always in CZK.
occasionNoThe occasion the buyer named.
ready_nowNoOnly bouquets already made and waiting (fastest).
deliver_byNoHH:MM (24 h): must arrive by then. Without date it means today.
fulfilmentNodelivery (default) or pickup at the florist's shop.
free_deliveryNoOnly 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_czkNoBouquet price limit in CZK (delivery not included).
budget_min_czkNo

Output Schema

NameRequiredDescriptionDefault
emptyNo
resultsYes
currencyNo
interpretedYes
total_foundYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / flowers
      Added value: +{
      +  "description": "Plant ids the bouquet must hold ANY of, as results show them under `flowers` (e.g. [\"rosa\"], [\"rosa\", \"hydrangea\"]). A plant covers its forms (spray roses are roses).",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. Changed3 schema fields changed
    • 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"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / occasion / description
      Previous value: -"Only when the buyer named the occasion. Never assume 'sympathy'."New value: +"The occasion the buyer named."
  4. Changed1 schema field changed
    • changedOutput schema / properties / results / items / properties / earliest / properties / day / enum
      Previous value: -[
      -  "today",
      -  "tomorrow",
      -  "later"
      -]New value: +[
      +  "today",
      +  "tonight",
      +  "tomorrow",
      +  "later"
      +]
  5. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/open-world safety, and the description adds genuinely non-obvious behavior: results render to the buyer as a carousel, results are ordered by the storefront's recommendation, and with no date/deliver_by every result carries its earliest time. That is real context beyond the structured fields.

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?

Scope, return contents, input shape, side effect and exclusions are packed into four dense sentences with the most decision-relevant information (Prague, concrete bouquets, carousel) front-loaded. No sentence is 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?

With 18 params but an output schema and rich annotations, the definition still covers what an agent needs: eligibility guarantees, ordering, the empty-date fallback, the carousel side effect, and geographic bounds. Nothing material is missing for correct invocation.

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 description coverage is 94%, so the baseline is 3, but the description adds a useful framing of the input groups ('free text, occasion, budget, where, date and a deliver-by time') that helps an agent map buyer speech onto parameters. It doesn't add per-parameter syntax beyond the schema, keeping it below a 5.

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 concrete verb and resource ('returns only bouquets that can really arrive at the given place and time') and pins the geography to Prague, immediately separating it from sibling tools like get_bouquet or quote_order. An agent can tell exactly what this returns without opening the 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?

Explicitly frames the trigger ('Use this when the buyer wants flowers delivered in Prague... and you need concrete bouquets') and gives exclusions ('Not for general flower advice or for orders outside Prague'). It does not name a specific sibling to use instead for detail/advice, so it stops just short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources