Skip to main content
Glama

CielStay

by com.cielstay
OverviewDiscussionsAdmin

Get a multi-unit property

get_property
Read-onlyIdempotent

Every unit at one multi-unit property: a hotel, glamping site or building whose units share a booking site and a location. Search results carry readyToBook.property.id when a home is one of several such units. Returns the property (name only where the operator's own unit titles share it), and each unit with its label, bedrooms, guests, CielStay page and readyToBook. With checkIn and checkOut, each unit's readyToBook also carries availability and the total on the host's site for those dates (up to 30 units).

Input Schema

NameRequiredDescriptionDefault
idYesThe property id (readyToBook.property.id from a search result).
guestsNoNumber of guests. Defaults to 2.
checkInNoArrival date, YYYY-MM-DD.
checkOutNoDeparture date, YYYY-MM-DD.

Output Schema

NameRequiredDescriptionDefault
foundNo
unitsNo
messageNo
propertyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / properties / property / additionalProperties
      Added value: +true
    • addedOutput schema / properties / property / properties
      Added value: +{}
    • addedOutput schema / properties / property / type
      Added value: +"object"
    • addedOutput schema / properties / units / items
      Added value: +{
+  "$ref": "#/properties/property"
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "found": {
+      "type": "boolean"
+    },
+    "message": {
+      "type": "string"
+    },
+    "property": {},
+    "units": {
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  3. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new context: the property name is only returned where the operator's unit titles share it, and per-unit availability enrichment only occurs when dates are supplied, with a documented cap of up to 30 units.

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?

Content is front-loaded — the resource definition comes first, then data provenance, then return shape, then the date-dependent behavior. The middle parenthetical about name sharing is awkwardly compressed, but no sentence is filler.

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?

Given an output schema exists, the description need not explain returns, yet it still summarizes per-unit fields and the 30-unit cap. Combined with the id provenance and date-dependent behavior, an agent has everything needed to select and call this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning beyond the schema: checkIn/checkOut are not merely dates but switches that turn on availability and total price on the host's site per unit, and the id is identified as coming from readyToBook.property.id. The guests parameter is left unexplained beyond the schema.

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+resource ('Every unit at one multi-unit property') and immediately defines what counts as a property — a hotel, glamping site or building whose units share a booking site and location. That definition, plus the pointer that search results carry readyToBook.property.id for such homes, distinguishes it clearly from get_listing_details.

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 a concrete trigger: use this when a search result carries readyToBook.property.id because the home is one of several units. It also states the conditional benefit of supplying checkIn/checkOut. It stops short of naming an alternative tool (e.g. get_listing_details) or stating when not to call it.

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

All CielStay 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