The Flowers Directory

Delivery guidance for a venue

get_delivery_location_guidance

Read-onlyIdempotent

Return practical guidance for sending flowers to a specific kind of place: funeral_home, place_of_worship, hospital, residence, business, senior_living. Covers which arrangement types are appropriate and which to avoid, venue rules (such as hospital units that do not allow flowers), what details the florist needs, which checkout field each detail goes in, timing, and suggested search filters. With a city and state or ZIP, also lists funeral homes (for funeral_home) or hospitals (for hospital) in that city from the directory, with addresses.

Input Schema

Name	Required	Description
`zip`	No	ZIP code; used to find the city when no city is given.
`city`	No	City name, for local venue listings.
`limit`	No	Maximum venue listings to return.
`state`	No	State name or 2-letter code, used with city.
`location_type`	Yes	One of: funeral_home, place_of_worship, hospital, residence, business, senior_living. Common words such as church, nursing home, office or home are accepted.

Output Schema

Name	Required	Description	Default
`avoid`	No
`label`	Yes
`guides`	No
`timing`	No
`collect`	No
`appropriate`	No
`budget_note`	No
`local_venues`	No
`location_type`	Yes
`checkout_fields`	No
`suggested_searches`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "appropriate": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "avoid": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "budget_note": {
+      "type": "string"
+    },
+    "checkout_fields": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "collect": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "guides": {
+      "items": {
+        "properties": {
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "title",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "label": {
+      "type": "string"
+    },
+    "local_venues": {
+      "properties": {
+        "city": {
+          "type": "string"
+        },
+        "city_page": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "error": {
+          "type": "string"
+        },
+        "location_note": {
+          "type": "string"
+        },
+        "note": {
+          "type": "string"
+        },
+        "state": {
+          "type": "string"
+        },
+        "total_listed": {
+          "type": "integer"
+        },
+        "type": {
+          "type": "string"
+        },
+        "venues": {
+          "items": {
+            "properties": {
+              "address": {
+                "type": "string"
+              },
+              "name": {
+                "type": "string"
+              },
+              "phone": {
+                "type": "string"
+              },
+              "verified_date": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "name"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "required": [],
+      "type": "object"
+    },
+    "location_type": {
+      "type": "string"
+    },
+    "suggested_searches": {
+      "items": {
+        "properties": {
+          "args": {
+            "type": "object"
+          },
+          "for": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "for",
+          "args"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "timing": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "location_type",
+    "label"
+  ],
+  "type": "object"
+}

AddedOct 20, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive), so the description's job is to add semantics — and it does: it discloses that directory listings appear only for funeral_home and hospital types and only when city+state or ZIP is supplied. It doesn't explain how the guidance degrades without a location, which is the remaining gap.

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 core purpose in the first clause, with supporting enumeration after. The middle content list is dense but each item (venue rules, checkout field mapping, timing, search filters) tells the agent something it would otherwise have to discover by calling.

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?

Return values need not be described since an output schema exists, and the description adequately conveys scope, the required location_type, and the conditional territory-listing behavior. A fuller definition would note behavior when location_type is residence/business (no directory listing) and any validation failures.

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 baseline is 3; the description earns extra by explaining the interaction the schema cannot — that city/state or ZIP unlocks local venue listings and that listing type depends on location_type. It doesn't clarify what happens with city but no state, or how limit interacts, so not a 5.

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?

The description has a clear verb ('Return practical guidance') and a precisely enumerated resource (the six venue types) plus the content covered: arrangement suitability, venue rules, checkout fields, timing, and filters. It does not explicitly distinguish itself from the closest sibling, check_delivery, so an agent must infer the boundary between 'guidance' and 'delivery feasibility'.

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?

Usage is implied rather than stated: this is the tool to consult when sending to a funeral_home, hospital, etc. The description does give a conditional trigger ('With a city and state or ZIP, also lists funeral homes... or hospitals'), but it never says when to prefer this over check_delivery or find_local_florists, nor any exclusions.

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?