Skip to main content
Glama

Guest2Host

Ask the owner a question

send_inquiry

Send a traveler's question to the owner of a stay by email, for example about early check-in or a longer stay. The owner replies to the traveler's email directly. Use only with the traveler's name, email and question, and only after they have agreed to send it. This does not book or hold the dates.

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": {
      "slug": "<slug>",
      "guestName": "<guestName>",
      "guestEmail": "<guestEmail>",
      "message": "<message>"
    },
    "name": "send_inquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe stay's slug, from search_stays
guestsNo
checkInNoCheck-in date, YYYY-MM-DD
messageYesThe traveler's question, 10–2000 characters
checkOutNoCheck-out date, YYYY-MM-DD
guestNameYesThe traveler's name
guestEmailYesWhere the owner should reply
guestPhoneNoOptional phone number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare openWorldHint, non-idempotent, non-destructive. The description adds real context beyond them: the message goes out as email to a third party, the owner replies directly to the traveler rather than through the system, consent is required, and no dates are held. It does not spell out that repeated calls send duplicate emails or what happens on delivery failure.

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 short sentences ordered by importance: what it does, how the reply flows, then the consent precondition and negative scope. No filler or repetition.

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?

For an 8-parameter outbound-message tool with no output schema, the description covers purpose, consent, and reply routing well. It leaves the optional date/guest/phone parameters and any failure behavior unaddressed, which is a minor gap given strong schema coverage.

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 coverage is 88%, so the schema already documents slug, dates, message length, and email semantics. The description only restates the required name/email/question set and says nothing about the optional guests, checkIn/checkOut, or guestPhone fields, so it adds little beyond the schema baseline.

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 ('Send a traveler's question to the owner of a stay by email') plus the channel and example topics (early check-in, longer stay). This clearly separates it from booking-oriented siblings like check_dates or get_booking_link.

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?

Gives an explicit precondition ('only after they have agreed to send it') and a negative scope statement ('does not book or hold the dates'), which routes the agent away from booking tools. It stops short of naming a specific alternative to use when the traveler wants to book.

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