Skip to main content
Glama

Direct Hotels

Search hotels

search_hotels
Read-onlyIdempotent

Hotels in a city or district, each with the link to book on the hotel's own website, its rating, stars and a short description. Use when the user asks where to stay somewhere, for hotels in a place, or for hotels with a pool, parking, pets allowed or a star rating. Districts, regions and spellings resolve to their city ("Shinjuku", "Badung Regency", "Marrakesh", "Roma"). City names repeat across countries, so country changes the answer ("Brisbane" alone is the one in California). Where the directory lists nothing, the result is covered: false with covered places instead. For one named hotel, use get_hotel.

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

Input Schema

NameRequiredDescriptionDefault
cityYesCity, neighbourhood or district name, e.g. "Paris", "Shinjuku".
limitNoDefault 5, max 20.
starsNoStar class filter. Note: 84% of the directory has no published star class, so this hides most hotels — prefer sorting by rating.
clientNoOptional: your product or agent name, e.g. "Claude". Not used by the tool; recorded only for the public count of which assistants use the directory.
countryNoCountry name or ISO code, e.g. "Australia" or "AU". Disambiguates repeated city names.
sort_byNoDefault: rating.
amenitiesNoOnly hotels whose own website mentions all of these. Read from hotel sites, which covers about a quarter of the directory, so an empty result means "not mentioned", not "not available".

Output Schema

NameRequiredDescriptionDefault
queryYes
totalYes
hotelsYes
coveredYes
guidanceNo
widened_toNo
alternativesNo
searched_insteadNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior: district/region/spelling normalization, country-based disambiguation, and the covered:false outcome. The star and amenity coverage caveats are actually carried by the schema field descriptions rather than this text, so the description itself adds moderate rather than exceptional context.

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?

Front-loaded with the resource and return content, then usage triggers, then normalization rules, then the sibling routing. Every sentence carries distinct information; there is no filler or repetition.

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?

Output schema exists, so return-shape detail is unnecessary, yet the description still explains the covered:false case that an agent would otherwise misread as failure. For a 7-parameter lookup with full schema coverage and annotations, nothing needed to call or interpret it 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 the baseline is 3; the description earns above that by explaining that districts and alternate spellings resolve to a city and that `country` changes the answer for repeated city names ("Brisbane" is the California one). It does not restate the enumerated amenity or sort options, which the schema handles.

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 plus the exact payload returned (booking link, rating, stars, short description). It explicitly distinguishes itself from the sibling get_hotel for the single-hotel case, so an agent can pick correctly without opening either schema.

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

Usage Guidelines5/5

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

Gives concrete trigger phrases ("where to stay", hotels with pool/parking/pets/star rating) and an explicit exclusion routing to get_hotel for one named hotel. It also tells the agent how to interpret an empty/negative result via covered: false, which is usage guidance, not just behavior.

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