Skip to main content
Glama

HotelMonitor hotel prices

Find hotel deals

find_hotel_deals
Read-onlyIdempotent

Current hotel deals from the latest scans (at most 20): hotels priced below their typical level, optionally for one destination, check-in month or maximum nightly price. Prices are tax-inclusive nightly figures for two adults from past scans (the Agoda share is an estimate of tax), not a live quote. Each deal includes page_url (price history) and book_url (a booking-site link with the dates filled in) for checking the current price. Agoda's Mega Sale runs from 16 to 30 November. It is Agoda's own sale and HotelMonitor has not checked Agoda's prices. Details: https://hotelmonitor.co.uk/black-friday-hotel-deals-2026

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_hotel_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
viaNoOptional short name of your app or assistant (lower-case letters, digits, - or _), used in booking links so we can see where visits come from.
monthNoYYYY-MM check-in month.
max_priceNoMaximum price per night in GBP.
destinationNo

Output Schema

NameRequiredDescriptionDefault
hintNo
dealsNo
errorNo
notesNo
page_urlNo
requestedNo
suggestionsNo
valid_destinationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedOutput schema / anyOf
      Previous value: -[
      -  {
      -    "required": [
      -      "deals",
      -      "page_url",
      -      "notes",
      -      "data_as_of"
      -    ]
      -  },
      -  {
      -    "required": [
      -      "error"
      -    ]
      -  }
      -]New value: +[
      +  {
      +    "required": [
      +      "deals",
      +      "page_url",
      +      "notes"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "error"
      +    ]
      +  }
      +]
    • removedOutput schema / properties / data_as_of
      Removed value: -{
      -  "type": "string"
      -}
    • addedOutput schema / properties / deals / items / properties / scanned_at
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / deals / items / properties / typical_basis
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / properties / deals / items / properties / typical_per_night_gbp / type
      Previous value: -[
      -  "number",
      -  "null"
      -]New value: +"number"
    • changedOutput schema / properties / deals / items / required
      Previous value: -[
      -  "hotel",
      -  "checkin",
      -  "checkout",
      -  "price_per_night_gbp",
      -  "typical_per_night_gbp",
      -  "page_url",
      -  "book_url"
      -]New value: +[
      +  "hotel",
      +  "checkin",
      +  "checkout",
      +  "price_per_night_gbp",
      +  "page_url",
      +  "book_url"
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses a 20-result cap, that prices are tax-inclusive nightly figures for two adults derived from past scans, that the Agoda tax share is an estimate, and that Agoda's own sale prices were not verified by HotelMonitor. These are substantive freshness and reliability caveats an agent needs. It stops short of describing ordering or what happens when no deals match.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Core purpose, filters, and price caveats are front-loaded and well ordered. However, the Mega Sale paragraph and external URL are largely promotional and do not help an agent decide or invoke correctly, diluting an otherwise tight definition.

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?

Given an output schema that covers return fields and annotations that cover safety, the description supplies everything else an agent needs: data freshness, result cap, price basis, the role of page_url and book_url, and caveats about unverified sale prices.

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 75%, and the description adds real meaning: all three filters are optional and narrow to a single destination, one check-in month, or a maximum nightly price, and it clarifies that prices (and therefore max_price) are tax-inclusive nightly figures for two adults. The `via` attribution parameter is left to the schema, which already documents it fully.

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?

Specific verb and resource: it returns current hotel deals, defined precisely as "hotels priced below their typical level," with an explicit result cap of 20. It also distinguishes itself from a live-quote tool by stating the figures come from past scans and are "not a live quote," which helps separate it from check_hotel_price without naming it.

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 context is implied rather than stated: the description explains that prices are historical and points to page_url/book_url "for checking the current price," which nudges the agent toward a live-price tool when freshness matters. There is no explicit when-to-use/when-not-to-use statement or named alternative.

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