Déstaire

Get a destination

get_destination

Read-onlyIdempotent

One destination and its stays: the first 10 and the total, or all of them with detail "full".

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	The destination's slug, the last part of its URL.
`detail`	No	"concise" (the default): the start of the answer and a count, to save context; "full": all of it.	concise
`country`	No	The country, when two destinations share a slug.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`name`	Yes
`note`	No
`stays`	Yes
`total`	Yes
`country`	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"
+]

Changed4 schema fields changedSep 24, 2026

addedInput schema / properties / detail

Added value: +{
+  "default": "concise",
+  "description": "\"concise\" (the default): the start of the answer and a count, to save context; \"full\": all of it.",
+  "enum": [
+    "concise",
+    "full"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / note
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / total

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

changedOutput schema / required

Previous value: -[
-  "name",
-  "url",
-  "country",
-  "stays"
-]New value: +[
+  "name",
+  "url",
+  "country",
+  "total",
+  "stays"
+]

First observedSep 24, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds genuinely useful behavioral context beyond them: the default response is truncated to the first 10 stays with a total count, and detail=full returns everything. That truncation/context-saving behavior is not expressed in the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no filler, which is good, but the structure is choppy: the clause 'the first 10 and the total, or all of them with detail "full"' is syntactically loose and slightly ambiguous about what is truncated (the stays vs. the destination).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and annotations cover the safety profile, so the remaining burden is light. However, for a tool whose default response is silently truncated, the description could do more on error/not-found and ambiguous-slug behavior, and usage guidance is thin.

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 slug, detail, and country are already documented in the schema, making 3 the baseline. The description gestures at the detail enum's effect but does not add syntax, format, or fallback meaning beyond what the schema string already says.

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 (retrieve one destination plus its stays) and uses 'One destination' to distinguish from the sibling list_destinations. It does not name the sibling explicitly, but an agent can tell single-fetch from list semantics 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 only implied: 'One destination' signals single-record lookup versus list_destinations, and the detail explanation hints at when a lighter response is wanted. There is no explicit when-to-use/when-not guidance or alternative named.

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?