Skip to main content
Glama

Happy Island Cottage booking

Get an exact quote

get_quote
Read-only

Exact all in price for one home and date range, from the same engine as the site's booking form: nightly subtotal, any discount, cleaning fee, pet fee, 7% sales tax plus surtax, 6% tourist development tax, total, and the payment schedule (20% deposit at booking and the balance 45 days before check in, or full payment when check in is 45 days away or less; returning guests with their returning guest code pay no deposit and no pet fee). Errors (each with a one sentence message): UNKNOWN_PROPERTY, BAD_DATES, PAST_DATES, BEYOND_HORIZON (last night after 2027-12-31; carries lastBookableDate), MIN_NIGHTS, UNAVAILABLE, OVER_CAPACITY (carries maxGuests). Sending a request does not hold your dates: they are reserved when the deposit or full payment clears. Check in 3:00 PM, check out 10:00 AM. Read only; nothing is booked or held.

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>"
    },
    "name": "get_quote"
  }
}

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
guestsNoNumber of guests, counted against the home's capacity
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

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 (adds the dog fee)"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.6/5.0
Behavior5/5

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

Goes far beyond the readOnlyHint/openWorldHint annotations: it discloses the exact tax rates, deposit rules (20% at booking, balance 45 days out, full payment at 45 days or less), returning-guest exceptions, check-in/out times, and the critical non-holding behavior. It also documents every error code with when it fires and which ones carry payloads (BEYOND_HORIZON -> lastBookableDate, OVER_CAPACITY -> maxGuests).

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?

Core purpose is front-loaded, then pricing detail, then errors, then the booking caveat – a sensible order with essentially no filler. It is a dense single block and the parenthetical error enumeration and payment-schedule clause are hard to scan, which is the only reason it isn't a 5.

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?

With no output schema, the description carries the return-value burden and does so fully by enumerating every line item, the total, and the payment schedule. Combined with documented failure modes, tax rates, and the non-holding caveat, an agent has everything needed to call and interpret this tool 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 the baseline is 3, but the description adds real meaning the schema lacks: it explains that the code parameter can carry a returning guest code which waives the deposit and pet fee, and it links the dog parameter to the pet fee line. Guest capacity and date-horizon constraints are also clarified through the error list.

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 precise verb and resource: compute the exact all-in price for one home and date range, enumerating the returned line items (nightly subtotal, discounts, fees, two taxes, total, payment schedule). It also notes it is the same engine as the booking form, so an agent can distinguish it from check_availability (availability only) and request_booking (mutating) without opening a schema.

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?

The ending 'Read only; nothing is booked or held' plus 'Sending a request does not hold your dates: they are reserved when the deposit or full payment clears' clearly frames this as the pricing step, not the booking step. It stops short of naming check_availability or request_booking as the explicit alternative for those tasks, so the routing is strongly implied rather than spelled out.

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