The Flowers Directory

Create a prefilled checkout link

create_prefilled_checkout

Save delivery details for one arrangement on theflowersdirectory.com for 24 hours and return a checkout link that opens with the arrangement in the cart and those details filled in, plus the price breakdown (exact total when a ZIP is given). Takes the recipient's name, venue, room or unit, card message and special instructions, with the ZIP and delivery date. It does not place an order or take payment: the customer adds the street address and phone numbers, checks the details, pays and places the order on the site.

Input Schema

Name	Required	Description
`zip`	No	Recipient ZIP code; fills the ZIP field and gives an exact total including tax.
`code`	Yes	Arrangement product code, e.g. T163-1A.
`date`	No	Requested delivery date, YYYY-MM-DD. Requires zip. Selected at checkout if available.
`client`	No	Name of the assistant or app making the request (used only for attribution, e.g. "chatgpt").
`venue_name`	No	Funeral home, hospital, church or business name, if delivering to one.
`card_message`	No	Message printed on the enclosure card, including who it is from.
`room_or_unit`	No	Apartment, suite, floor or hospital room number.
`recipient_name`	No	Recipient's full name (for a funeral, e.g. "Family of Jane Smith").
`special_instructions`	No	Notes for the florist, e.g. the deceased's name and service time for a funeral.

Output Schema

Name	Required	Description	Default
`pricing`	Yes
`product`	Yes
`delivery`	No
`product_url`	Yes
`checkout_url`	Yes
`how_to_order`	Yes
`expires_in_hours`	Yes
`prefilled_fields`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "checkout_url": {
+      "type": "string"
+    },
+    "delivery": {
+      "properties": {
+        "available": {
+          "type": [
+            "boolean",
+            "null"
+          ]
+        },
+        "date": {
+          "type": "string"
+        },
+        "note": {
+          "type": "string"
+        },
+        "same_day_cutoff": {
+          "type": "string"
+        },
+        "zip": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "zip",
+        "date",
+        "available",
+        "note"
+      ],
+      "type": "object"
+    },
+    "expires_in_hours": {
+      "type": "number"
+    },
+    "how_to_order": {
+      "type": "string"
+    },
+    "prefilled_fields": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "pricing": {
+      "properties": {
+        "currency": {
+          "type": "string"
+        },
+        "delivery_fee": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "note": {
+          "type": "string"
+        },
+        "price": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "tax": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "total": {
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "currency",
+        "tax",
+        "total",
+        "note"
+      ],
+      "type": "object"
+    },
+    "product": {
+      "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"
+    },
+    "product_url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "product",
+    "pricing",
+    "checkout_url",
+    "how_to_order",
+    "product_url",
+    "prefilled_fields",
+    "expires_in_hours"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 20, 2026

changedInput schema / properties / code / description

Previous value: -"Product code from search_arrangements, e.g. T163-1A."New value: +"Arrangement product code, e.g. T163-1A."

AddedOct 20, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Adds substantial context beyond annotations: the 24-hour retention window, that it does nothing irreversible (no order, no payment), what exactly gets prefilled, and what the customer must still supply. This makes the non-idempotent, open-world write safe and predictable to reason about.

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 front-loaded sentences that open with the effect and lifetime before listing inputs and non-goals. Dense but every clause carries information; only the input enumeration mildly duplicates the schema.

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?

Given an output schema and annotations, the description covers the remaining gaps: lifetime of the saved data, safety boundaries, and division of labor between agent and customer. Nothing needed to invoke 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 100% and every parameter already documents itself, including the zip→exact total relationship. The description groups parameters by purpose but adds no syntax or format detail beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a precise verb+resource: saves delivery details for one arrangement for 24 hours and returns a checkout link with the cart prefilled plus a price breakdown. The 'does not place an order or take payment' clause separates it from order-placement flows, though it never names the close sibling get_checkout_link, leaving a possible ambiguity unresolved.

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?

Clear context for when to use it: when the customer wants a prefilled link rather than an immediate order, with the exact handoff described (customer adds street address, phone, pays). No explicit when-not or named alternative (e.g. get_checkout_link) is given, so it falls 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.

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?