Skip to main content
Glama

Message the host

contact_host

Sends a traveller's first message to a home's host through CielStay: questions, dates and party, a request to book, or a monthly or long-stay inquiry. Free. guestEmail must be the traveller's own address: CielStay emails it a confirmation link, and the message goes on only after the traveller opens it and signs in or creates a free account. Available for homes that carry messageHostUrl: hostReach in the reply is "host" (the host manages the home on CielStay) or "possible_contact" (a contact published on the operator's own site is told a guest asked; they may not answer). For any other home it is refused with hostReach "none", and bookUrl is the way to the host. CielStay never takes bookings or payments; the host replies with their terms. Takes the id from search_vacation_rentals or get_listing_details. messageHostUrl is the same form for the traveller to send.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "listingId": "<listingId>",
      "guestEmail": "<guestEmail>",
      "message": "<message>"
    },
    "name": "contact_host"
  }
}

Input Schema

NameRequiredDescriptionDefault
petsNoNumber of pets
guestsNoNumber of guests
checkInNoArrival date, YYYY-MM-DD
messageYesThe message to the host, in the traveller's words: who is coming, why, and any questions
checkOutNoDeparture date, YYYY-MM-DD
listingIdYesThe home's CielStay id (or slug)
guestEmailYesThe traveller's own email address, which receives the confirmation link

Output Schema

NameRequiredDescriptionDefault
nextNo
errorNo
statusNo
successNo
hostReachNo
listingUrlNo
hostOnCielStayNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the two-step confirmation flow: guestEmail receives a confirmation link and the message is only sent after the traveller opens it and signs in or creates an account. It also declares the tool is free, that CielStay never takes bookings or payments, and explains the hostReach semantics including the limp 'possible_contact' case.

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?

The purpose and the free/confirmation constraints are front-loaded, and most sentences carry unique routing or behavioral information. It is dense and slightly run-on, with the closing messageHostUrl sentence adding marginal value, but there is little outright waste.

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 seven parameters, an output schema, and a multi-step confirmation gate, the description covers eligibility, the send flow, the alternative path, and the hostReach response semantics. An agent can decide whether to call it and what to expect without opening another tool.

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 the schema already documents all seven parameters. The description adds meaningful context beyond it: guestEmail must be the traveller's own address because it receives the confirmation link, and listingId should come from search_vacation_rentals or get_listing_details.

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?

States a specific verb and resource: sends a traveller's first message to a home's host through CielStay, and enumerates the message intents (questions, dates and party, booking request, long-stay inquiry). It also distinguishes the tool from the booking path by naming bookUrl as the alternative for ineligible homes.

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

Usage Guidelines5/5

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

Explicitly states the eligibility condition (home must carry messageHostUrl), the two possible hostReach outcomes, the refusal case with hostReach 'none', and directs the agent to bookUrl instead. It also names the sibling tools that supply the listingId, leaving little to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources