The Flowers Directory

Search flower arrangements

search_arrangements

Read-onlyIdempotent

Search The Flowers Directory catalog of fresh flower arrangements and plants for US florist delivery, by occasion (birthday, sympathy/funeral, get well, anniversary, romance, new baby, thank you and more), color, flower type, arrangement type (vase, basket, standing spray, wreath, casket spray and more), size, budget and free text. Every result includes the product code used by the other tools, the arrangement price, a photo URL, total_before_tax (price plus the flat $19.99 delivery fee) and, when known, structured attributes: arrangement type, size tier, height and width in inches, stem count, container and who it suits (sender_fit). Returns up to 20 matches, best match first.

Input Schema

Name	Required	Description
`size`	No	One of: small (under 14 in), medium (14 to 22 in), large (over 22 in), tribute (easel, casket and floor pieces for funerals).
`limit`	No
`query`	No	Free-text keywords matched against the title and description, e.g. "blue hydrangea in a vase" or "standing spray".
`budget`	No	Maximum all-in amount in USD before tax (arrangement price + $19.99 delivery). Use this for "around $110"-style requests.
`colors`	No	Colors that should appear in the arrangement (any match). Known values: red, pink, white, yellow, purple, lavender, orange, blue, green, cream, peach, coral, burgundy, gold, mixed.
`occasion`	No	One of: sympathy, birthday, romance, anniversary, get_well, new_baby, thank_you, mothers_day, congratulations, wedding, just_because. "funeral" is accepted as sympathy.
`min_price`	No	Minimum arrangement price in USD.
`flower_types`	No	Flower types that should appear (any match). Known values: roses, lilies, tulips, sunflowers, orchids, carnations, daisies, hydrangeas, alstroemeria, chrysanthemums, gerberas, lisianthus, snapdragons, dahlias, peonies, irises, delphinium, larkspur, gladiolus, calla lilies, freesia, ranunculus, asters, proteas, anthuriums, succulents, stock, poinsettia, plants, mixed.
`arrangement_type`	No	One of: vase_arrangement, basket, floor_basket, table_arrangement, centerpiece, plant, dish_garden, wreath, standing_spray, standing_heart, standing_cross, casket_spray, casket_adornment, urn_tribute. Common words like "vase", "spray", "easel", "casket" or "urn" are accepted.

Output Schema

Name	Required	Description	Default
`note`	No
`count`	Yes
`filters`	Yes
`currency`	Yes
`products`	Yes
`delivery_fee`	Yes
`total_matches`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 27, 2026

addedInput schema / properties / arrangement_type

Added value: +{
+  "description": "One of: vase_arrangement, basket, floor_basket, table_arrangement, centerpiece, plant, dish_garden, wreath, standing_spray, standing_heart, standing_cross, casket_spray, casket_adornment, urn_tribute. Common words like \"vase\", \"spray\", \"easel\", \"casket\" or \"urn\" are accepted.",
+  "type": "string"
+}

changedInput schema / properties / flower_types / description

Previous value: -"Flower types that should appear (any match). Known values: roses, lilies, tulips, sunflowers, orchids, carnations, daisies, hydrangeas, alstroemeria, chrysanthemums, gerberas, lisianthus, snapdragons, dahlias, peonies, irises, delphinium, larkspur, gladiolus, calla lilies, freesia, ranunculus, asters, proteas, anthuriums, succulents, plants, mixed."New value: +"Flower types that should appear (any match). Known values: roses, lilies, tulips, sunflowers, orchids, carnations, daisies, hydrangeas, alstroemeria, chrysanthemums, gerberas, lisianthus, snapdragons, dahlias, peonies, irises, delphinium, larkspur, gladiolus, calla lilies, freesia, ranunculus, asters, proteas, anthuriums, succulents, stock, poinsettia, plants, mixed."

addedInput schema / properties / size

Added value: +{
+  "description": "One of: small (under 14 in), medium (14 to 22 in), large (over 22 in), tribute (easel, casket and floor pieces for funerals).",
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "currency": {
+      "type": "string"
+    },
+    "delivery_fee": {
+      "type": "number"
+    },
+    "filters": {
+      "properties": {
+        "arrangement_type": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "budget": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "colors": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "flower_types": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "min_price": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "occasion": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "query": {},
+        "size": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [],
+      "type": "object"
+    },
+    "note": {
+      "type": "string"
+    },
+    "products": {
+      "items": {
+        "properties": {
+          "attributes": {
+            "properties": {
+              "arrangement_type": {
+                "type": "string"
+              },
+              "container": {
+                "type": "string"
+              },
+              "height_in": {
+                "type": "number"
+              },
+              "sender_fit": {
+                "type": "string"
+              },
+              "size_tier": {
+                "type": "string"
+              },
+              "stem_count": {
+                "type": "integer"
+              },
+              "width_in": {
+                "type": "number"
+              }
+            },
+            "required": [],
+            "type": "object"
+          },
+          "best_for": {
+            "type": "string"
+          },
+          "code": {
+            "type": "string"
+          },
+          "colors": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "delivery_fee": {
+            "type": "number"
+          },
+          "description": {
+            "type": "string"
+          },
+          "flower_types": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "image": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "occasions": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "price": {
+            "type": "number"
+          },
+          "title": {
+            "type": "string"
+          },
+          "total_before_tax": {
+            "type": "number"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "price",
+          "delivery_fee",
+          "total_before_tax"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_matches": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "currency",
+    "delivery_fee",
+    "filters",
+    "total_matches",
+    "count",
+    "products"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 20, 2026

changedInput schema / properties / query / description

Previous value: -"Free-text keywords matched against the title and description, e.g. \"blue hydrangea in a vase\"."New value: +"Free-text keywords matched against the title and description, e.g. \"blue hydrangea in a vase\" or \"standing spray\"."

First observedSep 24, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds real behavioral value on top: result cap of 20, best-match ordering, and the return payload including product code, photo URL, and total_before_tax defined as price plus the flat $19.99 delivery fee.

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?

Two sentences, front-loaded with the search scope before the return contract. It is dense but nearly every clause carries a distinct fact (filters, result cap, price semantics, structured attributes); a slightly tighter split of the long return sentence would improve scanability.

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 a 9-parameter, all-optional search tool with an output schema and full annotation coverage, the description is complete enough to call correctly: it explains the filter surface, the ranking/cap behavior, and the price semantics an agent must reason about. Nothing needed for a correct invocation 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 already 89%, so baseline is 3, but the description adds genuine nuance beyond the schema — notably that budget is all-in (price + $19.99 delivery) while min_price is arrangement price only, and it broadens the occasion vocabulary beyond the enum list. That distinction materially affects correct parameter use.

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 and resource ('Search The Flowers Directory catalog of fresh flower arrangements and plants') with the delivery scope ('US florist delivery'). The filtering dimensions named (occasion, color, flower type, arrangement type, size, budget, free text) let an agent separate this discovery tool from the detail/checkout siblings without opening any 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?

The description makes the usage context clear by enumerating the browsable dimensions and noting the return shape, so an agent knows this is the entry point for finding products. It does not, however, explicitly route to siblings ('use get_arrangement_details for full detail' or 'use check_delivery for serviceability'), so the when-not guidance is inferred rather than stated.

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

All The Flowers Directory 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?