Skip to main content
Glama
Sign In

The Flowers Directory

by com.theflowersdirectory
OverviewDiscussionsAdmin

Get a purchase link with pricing

get_checkout_link
Read-onlyIdempotent

Return the purchase link for an arrangement plus a price breakdown. With a recipient ZIP the breakdown includes the exact delivery fee, tax and order total; with a ZIP and date it also confirms delivery availability. Opening the link adds the arrangement to the cart and opens the cart panel; the customer clicks Checkout and enters the recipient address, delivery date, card message and payment there.

Input Schema

NameRequiredDescriptionDefault
zipNoRecipient ZIP code, for an exact total including tax.
codeYesArrangement product code, e.g. T163-1A.
dateNoRequested delivery date, YYYY-MM-DD. Requires zip.
clientNoName of the assistant or app making the request (used only for attribution, e.g. "chatgpt").

Output Schema

NameRequiredDescriptionDefault
pricingYes
productYes
deliveryNo
checkout_urlYes
how_to_orderYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+    },
+    "how_to_order": {
+      "type": "string"
+    },
+    "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"
+    }
+  },
+  "required": [
+    "product",
+    "pricing",
+    "checkout_url",
+    "how_to_order"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • 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."
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world behavior, while the description adds important non-obvious context: opening the link adds the arrangement to the cart and opens the cart panel. No annotation contradiction; auth and rate-limit details are not covered but are not central here.

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?

Three sentences, front-loaded with the tool purpose, then pricing conditions, then the post-link checkout flow. There is no repetition, and the longer sentence carries useful behavioral detail.

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?

An output schema exists, so return values need not be explained in detail. The description covers pricing conditions and link behavior; it only omits failure/unavailable-date behavior and explicit sibling routing.

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 100%, so the baseline is 3, but the description adds conditional meaning for zip and date beyond the schema field descriptions: exact delivery fee, tax, total, and delivery availability with date. Code and client semantics remain delegated to the schema.

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 specific verb and resource: 'Return the purchase link for an arrangement plus a price breakdown.' It describes the checkout-link context well, though it does not explicitly name a sibling alternative, so differentiation is clear but not fully explicit.

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

Usage Guidelines3/5

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

Explains how ZIP and ZIP+date change the result, but does not say when to choose this tool over check_delivery, create_prefilled_checkout, or next_available_delivery. Usage is implied by the checkout purpose rather than directly routed.

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 toolsInspect
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