Skip to main content
Glama

Price a hotel stay

quote_hotel_stay
Read-only

Gets a live supplier offer or MBD contract price (pricingSource) for hotels and dates. Books nothing and holds no room. An unverified price is not returned. PRICE_ON_REQUEST means no price is on file; the reply then carries pageUrl and contact. Supplier calls are limited daily. Needs check-in, check-out and guests. When nationality is omitted the price is for TR and the reply states nationalityUsed.

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": {
      "language": "<language>",
      "currency": "<currency>",
      "hotelIds": "<hotelIds>",
      "checkIn": "<checkIn>",
      "checkOut": "<checkOut>",
      "adults": "<adults>"
    },
    "name": "quote_hotel_stay"
  }
}

Input Schema

NameRequiredDescriptionDefault
adultsYesAdults; at most 6 people per room, 4 children.
checkInYesCheck-in date; at most 365 days from today (YYYY-MM-DD)
checkOutYesCheck-out date; the stay must be 1-30 nights (YYYY-MM-DD)
currencyYes
hotelIdsYeshotelId values (ids, not names).
languageYes
nationalityNoISO 3166-1 alpha-2 code (TR, AE, DE); optional, default TR. Changes the price.
childrenAgesNoAge of each child, one entry per child. No birth dates.

Output Schema

NameRequiredDescriptionDefault
quotesYes
handoffNo
deepLinkYes
quotedAtYes
disclaimerNo
generatedAtNo
deepLinkNoteNo
liveQuoteLimitNo
nationalityNoteNo
nationalityUsedNo
catalogueRefreshedAtNo
nationalityDefaultedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false), so the description correctly adds the traits they don't: a daily supplier-call limit, the 'unverified price is not returned' validation rule, and the PRICE_ON_REQUEST path that returns pageUrl and contact. These are concrete operational behaviors beyond structured fields, though the rate limit is left unquantified.

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 core purpose and every sentence carries a distinct fact (scope, validation, PRICE_ON_REQUEST, rate limit, requirements, nationality default). It reads as a dense telegraphic cluster rather than flowing prose, which slightly hurts scanability.

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?

With an output schema present, return values needn't be explained, and the description covers the key edge cases (PRICE_ON_REQUEST, nationality default, call limits). It is nearly complete, missing only a quantified rate limit and any note on what the pricingSource distinction means for the caller.

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 75% and the schema already documents dates, guest caps, hotelIds and the nationality default. The description mostly restates requirements ('Needs check-in, check-out and guests') and the nationality default rather than adding syntax or format meaning, so the baseline 3 applies.

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 ('Gets a live supplier offer or MBD contract price ... for hotels and dates') and immediately scopes it as non-transactional ('Books nothing and holds no room'). This lets an agent distinguish it from booking tools and from siblings like quote_transfer or list_hotels without opening the schema.

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

Usage Guidelines3/5

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

Usage is implied rather than explicit: 'Books nothing and holds no room' signals this is the pricing step, not a booking step, and 'Needs check-in, check-out and guests' gives prerequisites. However, no sibling is named and no when-not-to-use condition is stated, so routing among the quote_* tools is left 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