wemake.holiday

Search hotels with live prices

search_hotels

Read-only

Find hotels in a city, region, district or near a landmark for a stay, with live prices (total for the stay, per room). Optionally look for a specific hotel by name — typos and run-together names are fine. Returns up to 15 hotels with stars, guest rating, price and a link to book on wemake.holiday.

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

Input Schema

Name	Required	Description
`place`	Yes	city, region, district or landmark, e.g. 'Bangkok Sukhumvit' or 'Koh Samui'
`adults`	No	number of adults (1-9), default 2
`checkin`	Yes	arrival date YYYY-MM-DD
`checkout`	Yes	departure date YYYY-MM-DD
`language`	No	answer language, ISO code like en, de, fr (default en)
`hotel_name`	No	optional: name of a specific hotel to find (typos are fine)

Output Schema

Name	Required	Description	Default
`note`	No
`place`	Yes
`hotels`	Yes
`nights`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Adds real context beyond the read-only/open-world annotations: results are capped at 15 hotels, prices are the total for the stay per room, and each result carries stars, guest rating and a booking link. It does not mention rate limits, caching or whether prices are guaranteed, which keeps it short of a 5.

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

Conciseness5/5

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

Three sentences, front-loaded with what is searched and where, then the optional name mode, then the return shape. No filler or repetition.

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?

An output schema exists, so return values need not be explained in depth, yet the description usefully summarizes the 15-result cap and the price basis. Missing only guidance on date constraints or what happens when no hotels match.

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 100%, so the baseline is 3. The description reinforces that place accepts a city, region, district or landmark and that hotel_name tolerates typos and run-together names, but those points largely restate the schema, and adults/language/dates get no added meaning.

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?

States a specific verb (find) and resource (hotels) plus the search scope — city, region, district or landmark — and the key differentiator of live prices. It does not name a sibling such as browse_hotels or find_hotel, so an agent must infer the split from 'optionally look for a specific hotel by name'.

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?

Use is implied by 'for a stay, with live prices' and the optional name lookup, which hints at overlap with a name-lookup sibling. There is no explicit when-not-to-use statement or pointer to an alternative for browsing without dates.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All wemake.holiday tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?