Déstaire

Search stays

search_stays

Read-onlyIdempotent

Find hotels and private stays by plain words, with optional filters for country, destination, collection, amenities, and a nightly budget in euros. Best matches first. Gives each stay's page URL, place, short description, and "from" rate.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sort`	No	"relevance" (best match first) or "rate" (lowest rate first).	relevance
`limit`	No	The most stays to give.
`query`	No	What the reader wants, in plain words: "quiet hotel on Lake Como with a spa". Stays that match more words come first.
`country`	No	Only this country: a name or an ISO code, such as "France" or "FR".
`max_rate`	No	Only stays whose "from" rate is at most this many euros a night (a week rate counts a seventh). Stays with no rate are left out.
`amenities`	No	Only stays that have each of these, by word: "spa", "pool", "beach", "tennis".
`collection`	No	Only this collection: a name or a slug, such as "Coast". list_destinations lists them.
`destination`	No	Only this destination: a name or a slug, such as "Provence".

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	No
`stays`	Yes
`total`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 28, 2026
- changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```
- changedOutput schema / properties / stays / items / additionalProperties
```
Previous value: -falseNew value: +{}
```
- changedOutput schema / properties / stays / items / properties / destination / additionalProperties
```
Previous value: -falseNew value: +{}
```
- changedOutput schema / properties / stays / items / properties / rate / additionalProperties
```
Previous value: -falseNew value: +{}
```

Changed2 schema fields changedSep 28, 2026

addedOutput schema / properties / stays / items / properties / rate / properties / checked

Added value: +{
+  "anyOf": [
+    {
+      "format": "date",
+      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The day the rate was last read on the hotel's own booking engine (YYYY-MM-DD). Null when no date is recorded."
+}

changedOutput schema / properties / stays / items / properties / rate / required

Previous value: -[
-  "text",
-  "amount",
-  "currency",
-  "per"
-]New value: +[
+  "text",
+  "amount",
+  "currency",
+  "per",
+  "checked"
+]

Changed2 schema fields changedSep 25, 2026

addedOutput schema / properties / stays / items / properties / kind

Added value: +{
+  "description": "A hotel, or a private stay: a whole house or estate that one party rents.",
+  "enum": [
+    "hotel",
+    "private stay"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / stays / items / required

Previous value: -[
-  "name",
-  "slug",
-  "url",
-  "town",
-  "destination",
-  "country",
-  "lede",
-  "rate",
-  "photo"
-]New value: +[
+  "name",
+  "slug",
+  "url",
+  "kind",
+  "town",
+  "destination",
+  "country",
+  "lede",
+  "rate",
+  "photo"
+]

Changed2 schema fields changedSep 25, 2026

addedOutput schema / properties / stays / items / properties / photo

Added value: +{
+  "anyOf": [
+    {
+      "format": "uri",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "A card-size photo of the stay (3:2)."
+}

changedOutput schema / properties / stays / items / required

Previous value: -[
-  "name",
-  "slug",
-  "url",
-  "town",
-  "destination",
-  "country",
-  "lede",
-  "rate"
-]New value: +[
+  "name",
+  "slug",
+  "url",
+  "town",
+  "destination",
+  "country",
+  "lede",
+  "rate",
+  "photo"
+]

First observedSep 24, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint false, and openWorldHint false, so the safety profile is fully covered. The description's added behavior ('Best matches first') largely restates the schema's sort default of 'relevance', and the listed return fields are already exposed by the output schema, so it adds limited new behavioral context.

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 tight sentences, front-loaded with the core action, then filters, then result shape. No filler and nothing repeated unnecessarily.

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?

With an output schema present, the return-value sentence is a bonus rather than a necessity, and all eight parameters plus the safety annotations are well covered. The one gap is routing guidance relative to get_stay/list_destinations, which an agent would have to infer.

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%, so all eight parameters are documented in the schema, including the 'from' rate semantics and amenity matching. The description adds only the grouping phrase 'a nightly budget in euros' for max_rate, which is minor beyond what the schema already says. Baseline 3 applies when the schema does the heavy lifting.

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 description opens with a specific verb and resource ('Find hotels and private stays') and specifies the search modality ('by plain words'), which cleanly separates it from get_stay (single fetch) and the list_* siblings. An agent can identify this as the keyword-search entry point without opening the schema.

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 by 'with optional filters for country, destination, collection, amenities, and a nightly budget', which tells the agent this is the filtered discovery tool. However, no sibling is named and there is no when-not guidance (e.g., use get_stay when you already have an ID, use list_destinations to discover filter values).

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

All Déstaire 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?