Skip to main content
Glama

Happy Island Cottage booking

Send a booking request

request_booking
Destructive

Sends a booking request to the owner on the guest's behalf, priced by the same engine as get_quote. This is request to book: the owner confirms by email to the guest with a payment link, and nothing is charged now. Call it ONLY after the guest has seen the quote and explicitly asked you to send the request, and set guestApproved to true to confirm that. Every call reaches a real person: never send tests, duplicates or requests the guest has not approved. Errors: as get_quote, plus MISSING_CONTACT and GUEST_APPROVAL_REQUIRED. Sending a request does not hold your dates: they are reserved when the deposit or full payment clears. Cancellation: full refund when cancelled 30 or more days before arrival; inside 30 days the stay is not refundable, except that returning direct guests can cancel anytime and a hurricane warning or mandatory evacuation order for Manatee County covering the stay dates means a full refund whenever cancelled.

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": {
      "property": "<property>",
      "checkin": "<checkin>",
      "checkout": "<checkout>",
      "guests": "<guests>",
      "name": "<name>",
      "email": "<email>",
      "guestApproved": "<guestApproved>"
    },
    "name": "request_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
dogNoTrue if the guest brings a dog (adds the pet fee). The REST endpoint calls this parameter pets; this server accepts pets as an alias.
codeNoDiscount code, only if the guest already has one
nameYesGuest's full name
emailYesGuest's email; the owner replies here with the payment link
notesNoAnything the guest wants the owner to know (optional)
phoneNoGuest's phone (optional)
guestsYesNumber of guests
checkinYesCheck in date, YYYY-MM-DD
checkoutYesCheck out date, YYYY-MM-DD
propertyYeshappy-island-cottage = Happy Island Cottage, sleeps 6; happy-turtle-a = Happy Turtle A, sleeps 5; happy-turtle-b = Happy Turtle B, sleeps 4
guestApprovedYesMust be true: the guest saw this quote and asked you to send the request

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / dog / description
      Previous value: -"True if the guest brings a dog"New value: +"True if the guest brings a dog (adds the pet fee). The REST endpoint calls this parameter pets; this server accepts pets as an alias."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already flag a destructive, non-idempotent, open-world write, and the description adds substantial context beyond them: nothing is charged now, the owner confirms by email with a payment link, and the request does not hold dates until payment clears. It also discloses the error surface (MISSING_CONTACT, GUEST_APPROVAL_REQUIRED) and the full cancellation/refund policy, which an agent must be able to relay.

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-loads purpose, then preconditions, then errors, then cancellation — a sensible ordering with no filler sentences. The cancellation paragraph is dense and long relative to the rest, but every clause is policy the agent may need to quote to a guest, so it earns its place.

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 write with no output schema, the description covers preconditions, side effects, charge timing, date-hold behavior, error codes, and refund rules. The remaining gap is what the call returns on success (confirmation payload, identifier), which the agent must infer since no output schema exists.

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%, so every parameter including the guestApproved const and the property enum is already documented; that sets the baseline at 3. The description reinforces why guestApproved must be true and notes pricing parity with get_quote, but adds no format, alias, or validation meaning 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?

States a specific verb and resource ("Sends a booking request to the owner on the guest's behalf") and immediately scopes it as request-to-book rather than instant booking. The reference to get_quote establishes the pricing lineage, so an agent can distinguish this from the quote and availability siblings without reading schemas.

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 gate: "Call it ONLY after the guest has seen the quote and explicitly asked you to send the request," plus the mechanical confirmation via guestApproved=true. It also names prohibited invocations (tests, duplicates, unapproved requests) and points to get_quote as the prerequisite step, which is exactly the when/when-not routing 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