The Flowers Directory

Look up an order

get_order_status

Read-onlyIdempotent

Look up an existing order placed on The Flowers Directory, using the order number from the confirmation email and the email address used at checkout. Returns the items, scheduled delivery date, delivery city and whether that date is upcoming, today or past. It does not provide live courier tracking; for delivery confirmation, changes or cancellations it returns the order-help phone and text numbers.

Input Schema

Name	Required	Description	Default
`email`	Yes	Email address the purchaser used at checkout.
`order_number`	Yes	Order number from the confirmation email, e.g. 123456789.

Output Schema

Name	Required	Description	Default
`items`	Yes
`tracking`	Yes
`order_help`	Yes
`order_total`	Yes
`order_number`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "items": {
+      "items": {
+        "properties": {
+          "code": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "delivery_city": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "delivery_date": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "status": {
+            "type": "string"
+          },
+          "status_note": {
+            "type": "string"
+          },
+          "venue": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "status",
+          "status_note"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "order_help": {
+      "properties": {
+        "phone": {
+          "type": "string"
+        },
+        "text": {
+          "type": "string"
+        }
+      },
+      "required": [],
+      "type": "object"
+    },
+    "order_number": {
+      "type": "string"
+    },
+    "order_total": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "tracking": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "order_number",
+    "order_total",
+    "items",
+    "tracking",
+    "order_help"
+  ],
+  "type": "object"
+}

AddedOct 20, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds real value beyond that: it enumerates what is returned (items, scheduled date, city, temporal status) and explicitly scopes out live tracking, which is the main behavioral surprise an agent could hit.

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?

Front-loaded with the action and inputs, then the return payload, then the exclusion. Every sentence carries information; it is slightly longer than strictly necessary but 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?

An output schema exists, yet the description still usefully summarizes the returned fields, and it flags the absence of live tracking plus the fallback contact route. Nothing an agent needs to call this correctly or set expectations 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%, with both parameters self-documented, so the baseline is 3. The description corroborates the semantics (confirmation email, checkout email) but adds no syntax or format detail beyond what the schema already states.

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 ('look up an existing order') plus the exact identifying inputs (order number from confirmation email, checkout email). It implicitly separates itself from tracking tools by stating it does not provide live courier tracking, though it never names the sibling check_delivery explicitly.

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?

Gives clear usage context: use when you have the order number and checkout email. It also sets an explicit exclusion ('does not provide live courier tracking') and redirects to the returned help phone/text numbers for confirmation, changes or cancellations. It stops short of naming alternative sibling tools by name.

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?