Skip to main content
Glama

Déstaire

by com.destaire
OverviewDiscussionsAdmin

Get a stay

get_stay
Read-onlyIdempotent

One stay as its page shows it: description, address, location, website, "from" rate, amenities, collections, and photo URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesThe stay's slug, the last part of its URL.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
heroYesThe main photo at 2:1.
kindYesA hotel, or a private stay: a whole house or estate that one party rents.
ledeYes
nameYes
rateYesThe "from" rate: the lowest nightly price over the next six months, checked each week.
townYes
photosYes
addressYes
countryYes
websiteYes
locationYes
amenitiesYes
collectionsYes
descriptionYes
destinationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +{}
    • changedOutput schema / properties / amenities / items / additionalProperties
      Previous value: -falseNew value: +{}
    • changedOutput schema / properties / collections / items / additionalProperties
      Previous value: -falseNew value: +{}
    • changedOutput schema / properties / destination / additionalProperties
      Previous value: -falseNew value: +{}
    • changedOutput schema / properties / location / additionalProperties
      Previous value: -falseNew value: +{}
    • changedOutput schema / properties / rate / additionalProperties
      Previous value: -falseNew value: +{}
  2. Changed2 schema fields changed
    • addedOutput schema / 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 / rate / required
      Previous value: -[
-  "text",
-  "amount",
-  "currency",
-  "per"
-]New value: +[
+  "text",
+  "amount",
+  "currency",
+  "per",
+  "checked"
+]
  3. Changed2 schema fields changed
    • addedOutput schema / 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 / required
      Previous value: -[
-  "name",
-  "url",
-  "lede",
-  "description",
-  "town",
-  "destination",
-  "country",
-  "address",
-  "location",
-  "website",
-  "rate",
-  "amenities",
-  "collections",
-  "hero",
-  "photos"
-]New value: +[
+  "name",
+  "url",
+  "kind",
+  "lede",
+  "description",
+  "town",
+  "destination",
+  "country",
+  "address",
+  "location",
+  "website",
+  "rate",
+  "amenities",
+  "collections",
+  "hero",
+  "photos"
+]
  4. Changed2 schema fields changed
    • addedOutput schema / properties / hero
      Added value: +{
+  "description": "The main photo at 2:1.",
+  "format": "uri",
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "name",
-  "url",
-  "lede",
-  "description",
-  "town",
-  "destination",
-  "country",
-  "address",
-  "location",
-  "website",
-  "rate",
-  "amenities",
-  "collections",
-  "photos"
-]New value: +[
+  "name",
+  "url",
+  "lede",
+  "description",
+  "town",
+  "destination",
+  "country",
+  "address",
+  "location",
+  "website",
+  "rate",
+  "amenities",
+  "collections",
+  "hero",
+  "photos"
+]
  5. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description adds the shape of the payload ('as its page shows it' plus the field inventory), but says nothing about missing-slug behavior, error cases, or rate limits.

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?

A single front-loaded sentence with no filler. The field enumeration is mildly wasteful since an output schema already defines the return shape, but it costs little and reads cleanly.

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 description need not explain return values, and annotations cover the read-only/idempotent nature, so the core needs of a one-param lookup are met. The only meaningful gap is not telling the agent where a slug comes from (i.e., routing to search_stays).

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 the single 'slug' parameter is fully documented in the schema, including its pattern and that it is the last part of the stay's URL. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 ('get_stay' returns one stay) and previews the returned surface — description, address, location, website, rate, amenities, collections, photos. It is clear on its own, but never names or contrasts with the obvious sibling search_stays, so an agent must infer that this is the single-record fetch versus the filtered list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance and no exclusions. It does not say that a slug is required or that slugs come from search_stays/list_stays, nor when an agent should prefer this over search_stays for detail retrieval. Usage is only implied by the field list.

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

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