Skip to main content
Glama

All hotels in a place

browse_hotels
Read-only

All hotels in a place (from list_destinations), sorted by guest rating, 50 per page — with stars, guest rating, number of reviews, address, location and a link. Optional filters: minimum stars, minimum guest rating (0–10). No travel dates needed; for live prices use search_hotels.

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": {
      "country": "<country>",
      "place": "<place>"
    },
    "name": "browse_hotels"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNopage (50 hotels each), default 1
placeYesplace slug from list_destinations, e.g. bangkok
countryYescountry slug or ISO code, e.g. thailand
languageNoanswer language, ISO code (default en)
min_starsNooptional minimum stars (1-5)
min_ratingNooptional minimum guest rating (0-10)

Output Schema

NameRequiredDescriptionDefault
urlYes
pageYes
pagesYes
placeYes
totalYes
hotelsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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), so the description's contribution is the pagination model (50 per page, sorted by guest rating) and the returned field set, which are genuinely useful. It does not mention any rate limits or failure modes for unknown place/country slugs, leaving a small gap.

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 compact sentences with the scope, sort, page size, filters, and the sibling hand-off front-loaded; no filler or repeated phrasing.

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?

For a filtered, paginated list tool with an output schema and full annotation coverage, everything an agent needs to call it correctly is present: prerequisites, pagination, sorting, optional filters, and the alternative tool.

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 description coverage is 100%, so parameter meaning is already fully documented; the description's mention of the two optional filters and the list_destinations provenance largely restates the schema. Baseline 3 applies because the description adds little syntax or constraint information beyond structured fields.

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 concrete verb and resource ("All hotels in a place") plus sort order, page size, and returned fields, and explicitly contrasts itself with search_hotels for live prices. An agent can distinguish this from search_hotels and find_hotel 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 Guidelines5/5

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

Gives the prerequisite (place comes from list_destinations), the key condition (no travel dates needed), and the alternative for a different need (search_hotels for live prices). When-to-use and when-to-use-something-else are both spelled out.

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