Skip to main content
Glama

Hotel details

mb_hotel
Read-onlyIdempotent

Fetch a hotel's star rating, guest reviews, location, landmarks, amenities, and check-in rules using a city/hotel reference or numeric ID.

Instructions

One hotel: stars, guest rating (0-5) and latest reviews, location, landmarks, check-in rules, amenities, FAQ.

landmarks: distance in km (drive minutes). Review text is cut at 400 characters unless full_text. hotel is null after a numeric id: get the 'city/hotel' ref from mb_find_place(mode='hotel'). Prices: mb_hotel_rooms, mb_hotel_calendar.

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

Input Schema

NameRequiredDescriptionDefault
hotelYes'city_slug/hotel_slug' (e.g. 'mashhad/enghelab') or numeric id.
reviewsNoHow many of the latest guest reviews to include.
full_textNoReturn long texts uncut instead of clipped.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.0
    • changedInput schema / properties / hotel / description
      Previous value: -"Hotel as 'city_slug/hotel_slug' (e.g. 'mashhad/enghelab') or its numeric id (e.g. '8778')."New value: +"'city_slug/hotel_slug' (e.g. 'mashhad/enghelab') or numeric id."
    • removedInput schema / title
      Removed value: -"mb_hotelArguments"
  2. Changed4 schema fields changedv0.3.0
    • addedInput schema / properties / full_text
      Added value: +{
      +  "default": false,
      +  "description": "Return long texts uncut instead of clipped.",
      +  "type": "boolean"
      +}
    • removedInput schema / properties / hotel / title
      Removed value: -"Hotel"
    • removedInput schema / properties / reviews / title
      Removed value: -"Reviews"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "mb_hotelDictOutput",
      -  "type": "object"
      -}New value: +null
  3. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, openWorld and non-destructive, so the bar is lower. The description still adds real behavioral detail: review text is clipped at 400 characters unless full_text, landmarks report distance in km plus drive minutes, and (critically) the result is null when a bare numeric id is passed — a failure mode an agent could not infer from the schema.

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

Conciseness4/5

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

Short and front-loaded: return contents first, then field semantics, then the null-after-numeric-id warning, then pointers to sibling tools for pricing. The fragmentary style (missing verbs, line-broken clauses) costs a little readability but wastes no words.

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 3-parameter read tool with no output schema, the description covers what is returned, how reviews are truncated, how landmark distances are expressed, and how to obtain a valid reference — leaving nothing an agent needs to call it correctly.

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 would be 3. The description earns the extra point by quantifying the truncation threshold (400 characters) that the schema only calls 'clipped', and by spelling out the numeric-id-versus-slug consequence for the 'hotel' parameter.

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?

The opening enumerates exactly what comes back for a single hotel: stars, guest rating and latest reviews, location, landmarks, check-in rules, amenities, FAQ. That verb-less telegraphic style ('One hotel: ...') is clear enough, and it implicitly separates the tool from mb_hotel_rooms and mb_hotel_calendar by declaring prices to be handled elsewhere.

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 gives actionable routing: prices live in mb_hotel_rooms and mb_hotel_calendar, and the 'city/hotel' reference comes from mb_find_place(mode='hotel'). It does not explicitly contrast with mb_search_hotels or mb_city_hotels, but the inputs make the when-to-use obvious.

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