Skip to main content
Glama

BookResorts — hotel & resort booking

Hotel rooms and rates

get_hotel
Read-onlyIdempotent

A hotel's live rooms and rates for the dates: room names, size, occupancy, board (room only / breakfast / all-inclusive), refundability and the total price per option. Pass an option_id to create_booking_link.

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": {
      "hotel_id": "<hotel_id>",
      "checkin": "<checkin>",
      "checkout": "<checkout>"
    },
    "name": "get_hotel"
  }
}

Input Schema

NameRequiredDescriptionDefault
roomsNo
adultsNo
checkinYesYYYY-MM-DD
checkoutYesYYYY-MM-DD
hotel_idYes
children_agesNo

Output Schema

NameRequiredDescriptionDefault
noteNo
stayYes
hotelYes
roomsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "hotel": {
      +      "properties": {
      +        "address": {
      +          "type": "string"
      +        },
      +        "amenities": {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": "array"
      +        },
      +        "check_in": {
      +          "type": "string"
      +        },
      +        "check_out": {
      +          "type": "string"
      +        },
      +        "city": {
      +          "type": "string"
      +        },
      +        "country": {
      +          "type": "string"
      +        },
      +        "guest_rating": {
      +          "type": "number"
      +        },
      +        "hotel_id": {
      +          "type": "string"
      +        },
      +        "name": {
      +          "type": "string"
      +        },
      +        "reviews": {
      +          "type": "integer"
      +        },
      +        "stars": {
      +          "type": "number"
      +        }
      +      },
      +      "required": [
      +        "hotel_id",
      +        "name"
      +      ],
      +      "type": "object"
      +    },
      +    "note": {
      +      "type": "string"
      +    },
      +    "rooms": {
      +      "items": {
      +        "properties": {
      +          "options": {
      +            "items": {
      +              "properties": {
      +                "board": {
      +                  "type": "string"
      +                },
      +                "free_cancellation_until": {
      +                  "type": [
      +                    "string",
      +                    "null"
      +                  ]
      +                },
      +                "option_id": {
      +                  "type": "string"
      +                },
      +                "per_night_usd": {
      +                  "type": "number"
      +                },
      +                "refundable": {
      +                  "type": "boolean"
      +                },
      +                "total_price_usd": {
      +                  "type": "number"
      +                }
      +              },
      +              "required": [
      +                "option_id",
      +                "board",
      +                "refundable",
      +                "total_price_usd"
      +              ],
      +              "type": "object"
      +            },
      +            "type": "array"
      +          },
      +          "room": {
      +            "type": "string"
      +          },
      +          "size_sqft": {
      +            "type": [
      +              "integer",
      +              "null"
      +            ]
      +          },
      +          "sleeps": {
      +            "type": [
      +              "integer",
      +              "null"
      +            ]
      +          }
      +        },
      +        "required": [
      +          "room",
      +          "options"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "stay": {
      +      "properties": {
      +        "checkin": {
      +          "type": "string"
      +        },
      +        "checkout": {
      +          "type": "string"
      +        },
      +        "nights": {
      +          "type": "integer"
      +        },
      +        "rooms": {
      +          "type": "integer"
      +        }
      +      },
      +      "required": [
      +        "checkin",
      +        "checkout",
      +        "nights"
      +      ],
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "hotel",
      +    "stay",
      +    "rooms"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description adds real value beyond that by noting the rates are 'live' and enumerating what each option carries (board, refundability, total price), which tells the agent the data is perishable and quote-grade. It does not discuss caching, rate limits or pricing caveats such as taxes, but the annotations lower the bar.

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?

Two dense sentences with the core purpose front-loaded and no filler; every clause about board, refundability and price earns its place. The trailing 'Pass an option_id to create_booking_link' is compact but risks confusing an agent into looking for an option_id input parameter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value explanation is not strictly required, and the annotations cover the safety profile. However, for a six-parameter pricing tool, the description leaves the occupancy parameters (adults, children_ages, rooms) unexplained, which is the main gap an agent would hit when trying to get correct rates for a family or group.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%: checkin/checkout carry YYYY-MM-DD notes, but hotel_id, rooms, adults and children_ages are undocumented in the schema. The description only says 'for the dates' and never explains occupancy parameters (adults, children_ages, rooms), which directly affect pricing. The single parameter-like token it does mention, option_id, is not even an input of this tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and scope: live rooms and rates for a hotel for given dates, including board type, refundability and total price. It implicitly separates itself from search_hotels by being the rates/live-availability step, though it never names that sibling. The mention of 'option_id' slightly blurs the boundary because that value is an output, not an input here.

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 only implied: an agent can infer this is the tool to call after search_hotels to get bookable rate options, and the final sentence routes onward to create_booking_link. There is no explicit 'use this when / not when' or statement of prerequisites, so the agent must reconstruct the flow.

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