wemake.holiday

Find a hotel by name

find_hotel

Read-only

Find a specific hotel by its name — typos and run-together names are fine (e.g. 'MeeStyleGarrage'). Optionally narrow by country (ISO code) and place. Returns the best matches with id, address, stars, rating and link; use the id with get_hotel, or search_hotels for prices.

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

Input Schema

Name	Required	Description
`name`	Yes	hotel name (typos are fine)
`place`	No	optional city or district, e.g. Bangkok
`country`	No	optional ISO country code, e.g. TH — faster and more precise
`language`	No	answer language, ISO code (default en)

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, non-open-world), and the description adds behavior beyond them: tolerance for typos and run-together names, best-match ranking rather than exact matching, and the fields returned. That last part partly duplicates the output schema, and matching/ranking rules are not spelled out, keeping it just under the top mark.

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?

Two tight sentences, all signal. The core lookup behavior and fuzzy-matching caveat are front-loaded, with narrowing options and next-step routing trailing behind in the order an agent needs them.

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?

The tool is simple (one required parameter), an output schema exists, and the description still covers fuzzy matching, optional narrowing, and which id to feed into follow-on calls. Nothing an agent needs to invoke it correctly is missing.

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 baseline would be 3, but the description adds real meaning: country and place narrow the candidate set, and the name parameter tolerates typos and concatenated words. The "faster and more precise" hint for country also appears in the schema, so the gain is modest rather than substantial.

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?

"Find a specific hotel by its name" gives a concrete verb and resource, and the description immediately adds scope (name lookup, not browsing) plus the fuzzy-match caveat with a concrete example. An agent can distinguish this from search_hotels or browse_hotels 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?

It names two follow-on routes with their conditions ("use the id with get_hotel, or search_hotels for prices"), which implicitly tells the agent this tool is not the price-search path. It stops short of stating an explicit when-not or pointing to browse_hotels for city-only exploration, so it is clear context rather than full exclusions.

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?