Skip to main content
Glama

Schedule for a hotel guest (front desk)

book_for_hotel_guest
Destructive

Requires the connected Fold account of front-desk staff at a Fold partner hotel (the login must belong to the hotel's Fold business account). Schedules laundry pickup for a guest by room number at that hotel. billTo='hotel' (default) puts the order on the hotel's monthly Fold statement so the hotel can charge the guest's folio: no card link is sent and no card is charged. billTo='guest' sends the guest the usual card link instead and is priced at the hotel guest rates (see book_hotel_pickup); billTo='hotel' orders are priced on the hotel's Fold contract rates, with the same hotel order minimum (get_pricing → hotelGuestRates). Guest name, email and phone are still needed for status updates. returnPreference: same_day (bag at the desk before 9 AM), express_same_day (9 AM–noon, Express surcharge), next_day, or flexible. This creates a real order.

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": {
      "roomNumber": "<roomNumber>",
      "guestFirstName": "<guestFirstName>",
      "guestLastName": "<guestLastName>",
      "guestEmail": "<guestEmail>",
      "guestPhone": "<guestPhone>",
      "services": "<services>",
      "returnPreference": "<returnPreference>"
    },
    "name": "book_for_hotel_guest"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoFor this order only, e.g. "2 dress shirts on hangers, rush for 6 PM event".
billToNoDefault 'hotel' (on the hotel's monthly statement).
servicesYes
guestEmailYesFor order status updates and the receipt.
guestPhoneYesE.164 or US 10-digit, for pickup/delivery texts.
roomNumberYes
guestLastNameYes
guestFirstNameYes
idempotencyKeyNoUUID recommended. Retrying with the same key returns the same order.
hotelAccountNameNoOnly needed if this login belongs to more than one partner hotel.
returnPreferenceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / idempotencyKey / description
      Previous value: -"UUID recommended. Retrying with the same key returns the same booking."New value: +"UUID recommended. Retrying with the same key returns the same order."
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already flag this as a non-read-only, destructive, open-world operation, and the description adds substantive context beyond them: the exact tag order minimum, the two distinct rate regimes, the fact that no card is charged on hotel billing, the Express surcharge, and the blunt warning that this creates a real order. It stops short of describing what confirmation or order identifier comes back, which matters for a mutation with no output schema.

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?

Front-loaded with the authorization gate, then moves through billing → pricing → guest data → return options in a logical order, ending with the destructive-action warning. It is dense and long for a single paragraph, but almost every clause carries decision-relevant information; only the rate cross-references could be trimmed.

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 11-parameter destructive mutation with no output schema, the definition covers auth, pricing, billing side effects and return timing well enough to call the tool correctly. The gaps are around outcomes and recoverability — no mention of what a successful call returns or how to undo/cancel a mistaken order (cancel_order exists as a sibling but is not referenced).

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 55% across 11 parameters, so the description must compensate and largely does: billTo gets default and downstream consequences, returnPreference gets a timing window per enum value, roomNumber gets its scope (at that hotel), and the guest contact fields get their purpose (status updates, receipts, pickup texts). notes, services, idempotencyKey and hotelAccountName are left entirely to the schema, which covers them adequately.

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: schedules laundry pickup for a guest by room number at a Fold partner hotel. It explicitly separates itself from the closest sibling (book_hotel_pickup) by billing model and rate source, so an agent can choose between them without opening either schema.

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?

Gives an explicit prerequisite (the login must belong to the hotel's Fold business account) and a crisp when-to-use split: billTo='hotel' for folio charging with no card link, billTo='guest' to send the usual card link at guest rates. Timing windows for each returnPreference value are spelled out, which is exactly the selection guidance an agent needs.

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