The Flowers Directory

Find local florists

find_local_florists

Read-onlyIdempotent

List florists located in a US city from The Flowers Directory's city pages, with addresses, phone numbers when listed, and the date each listing was last verified. These are directory listings: an order placed through The Flowers Directory is made and delivered by a florist in the Florist One network, which may or may not be one of the listed shops.

Input Schema

Name	Required	Description
`zip`	No	ZIP code; used to find the city when no city is given.
`city`	No	City name, e.g. "Worcester".
`limit`	No
`state`	No	State name or 2-letter code, e.g. "MA".

Output Schema

Name	Required	Description	Default
`city`	Yes
`note`	Yes
`state`	Yes
`florists`	Yes
`city_page`	Yes
`total_listed`	Yes
`location_note`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "city": {
+      "type": "string"
+    },
+    "city_page": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "florists": {
+      "items": {
+        "properties": {
+          "address": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "phone": {
+            "type": "string"
+          },
+          "verified_date": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "location_note": {
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "state": {
+      "type": "string"
+    },
+    "total_listed": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "city",
+    "state",
+    "total_listed",
+    "florists",
+    "city_page",
+    "note"
+  ],
+  "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 establish that this is a read-only, idempotent, non-destructive, non-open-world lookup. The description adds meaningful behavioral context beyond the annotations: it identifies The Flowers Directory city pages as the source, notes that phone numbers are only included when listed, provides a last-verified date, and explains that ordering through The Flowers Directory may not involve one of the listed shops. That caveat is especially useful for preventing misuse.

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?

The description is two sentences with no wasted text. The core action and scope are front-loaded, and the important directory-listing caveat follows immediately. It is appropriately sized for a lookup tool.

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?

The description covers the tool's purpose, data source, returned fields, and an important limitation about ordering and fulfillment. Annotations cover safety traits and an output schema exists, so the description need not explain return values. Minor gaps remain around how zip and city inputs interact, but the schema already documents that behavior.

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 description coverage is 75%, with most parameters documented in the schema itself. The description adds no parameter-specific details and does not compensate for the undocumented limit parameter. Given that the schema carries most of the parameter meaning, a baseline score of 3 is appropriate.

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 uses a specific verb and resource: list florists in a US city from The Flowers Directory's city pages. It also states what the listing includes (addresses, phone numbers when available, last-verified date), making the tool's output scope clear. It does not explicitly name sibling tools, but it implicitly distinguishes directory lookup from ordering tools by clarifying that these are directory listings.

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?

The description implies the tool is for finding local florist listings in a US city, and the second sentence warns that these are directory listings rather than order-placement tools. However, it does not explicitly say when to use this versus siblings like check_delivery or search_arrangements, nor does it state exclusions or alternatives. Usage is therefore inferable but not fully guided.

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?