Custom Blinds Shop

get_delivery_estimate

Read-only

Explain the lead time for a new order. Production takes 5 to 7 working days once payment clears, outside peak seasons, then courier transit of about 2 to 5 working days. Returns the ranges and a plain-language summary safe to share. Never quote a dispatch or delivery date: weather and production set them. Call this when a customer asks 'when will it arrive?'.

Input Schema

Name	Required	Description	Default
`order_date`	No	ISO date string of the order placement date (e.g. '2026-05-18'). Defaults to today.

Output Schema

Name	Required	Description	Default
`summary`	Yes
`important`	Yes
`order_date`	No
`production_starts`	No
`expedited_available`	No
`delivery_after_dispatch`	Yes
`transit_working_days_max`	Yes
`transit_working_days_min`	Yes
`production_working_days_max`	Yes
`production_working_days_min`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 26, 2026

removedOutput schema / properties / estimated_dispatch_date
```
Removed value: -{
-  "type": "string"
-}
```
addedOutput schema / properties / production_starts
```
Added value: +{
+  "type": "string"
+}
```
removedOutput schema / properties / production_working_days
```
Removed value: -{
-  "type": "number"
-}
```
addedOutput schema / properties / production_working_days_max
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / production_working_days_min
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / transit_working_days_max
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / transit_working_days_min
```
Added value: +{
+  "type": "number"
+}
```

changedOutput schema / required

Previous value: -[
-  "order_date",
-  "production_working_days",
-  "estimated_dispatch_date",
-  "delivery_after_dispatch",
-  "expedited_available",
-  "summary",
-  "important"
-]New value: +[
+  "production_working_days_min",
+  "production_working_days_max",
+  "transit_working_days_min",
+  "transit_working_days_max",
+  "delivery_after_dispatch",
+  "summary",
+  "important"
+]

Changed1 schema field changedOct 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "delivery_after_dispatch": {
+      "type": "string"
+    },
+    "estimated_dispatch_date": {
+      "type": "string"
+    },
+    "expedited_available": {
+      "type": "boolean"
+    },
+    "important": {
+      "type": "string"
+    },
+    "order_date": {
+      "type": "string"
+    },
+    "production_working_days": {
+      "type": "number"
+    },
+    "summary": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "order_date",
+    "production_working_days",
+    "estimated_dispatch_date",
+    "delivery_after_dispatch",
+    "expedited_available",
+    "summary",
+    "important"
+  ],
+  "type": "object"
+}

First observedMay 28, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only disclose readOnlyHint=true, and the description adds substantially more: what the answer contains (ranges plus a shareable plain-language summary), the seasonal caveat ('outside peak seasons'), and a hard guardrail against quoting exact dispatch or delivery dates because weather and production determine them. That is real operational context an agent cannot get from the annotation.

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?

Four sentences, front-loaded with the substantive lead-time facts before the caveats and the call trigger. Dense and largely waste-free, though the 'plain-language summary safe to share' detail is the only clause that could be trimmed as the output schema already covers return shape.

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?

With an output schema present, return values need no explanation, and the description covers the remaining burden: what is estimated, the ranges' drivers, seasonal exceptions, the guardrail on quoting dates, and the triggering scenario. Nothing an agent needs in order to call and use this 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 description coverage is 100% and order_date is fully documented with an ISO example and a 'defaults to today' note. The description adds nothing about the parameter and never mentions that an order date can be supplied, so this sits at the baseline where the schema does all the work.

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

Purpose5/5

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

The first sentence states a specific verb and resource ('Explain the lead time for a new order'), and the scope is disambiguated by naming the contributing stages (production, then courier transit). No sibling tool in the list does delivery estimation, so the agent can identify this immediately.

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?

It gives an explicit trigger: 'Call this when a customer asks "when will it arrive?"'. It also constrains the answer ('Never quote a dispatch or delivery date'). It stops short of naming a when-not-to-use case or an alternative tool, but no sibling actually competes for this task.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Custom Blinds Shop 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.