Skip to main content
Glama
Sign In
mrbilit-mcp

mrbilit-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Hotel rooms and prices

mb_hotel_rooms
Read-onlyIdempotent

Fetch available hotel rooms and exact prices for given check-in and check-out dates, including rooms left, meal plans, and cancellation rules.

Instructions

Every room of a hotel with its exact price for the dates: whole stay, per night, rooms left, meals.

price_toman is the whole stay for one room after discount (prices do not depend on the guest count; choose rooms whose sleeps fits, and add up several rooms for a group). rooms_left 0 = full. cancellation is the hotel's refund rule. Empty rooms list = nothing free for these dates (try mb_hotel_calendar).

Input Schema

NameRequiredDescriptionDefault
hotelYesHotel as 'city_slug/hotel_slug' from mb_search_hotels, mb_city_hotels or mb_find_place, e.g. 'mashhad/enghelab'.
guestsNoOnly rooms that sleep at least this many (with extra beds), e.g. 3.
check_inYesCheck-in date YYYY-MM-DD, e.g. '2026-10-20'.
check_outYesCheck-out date YYYY-MM-DD, e.g. '2026-10-23' (1 to 30 nights).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.0
    • removedInput schema / properties / check_in / title
      Removed value: -"Check In"
    • removedInput schema / properties / check_out / title
      Removed value: -"Check Out"
    • removedInput schema / properties / guests / title
      Removed value: -"Guests"
    • removedInput schema / properties / hotel / title
      Removed value: -"Hotel"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "mb_hotel_roomsDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish this as a safe, idempotent, read-only lookup, so the description is free to add domain semantics instead: price is post-discount whole-stay, prices are independent of guest count, rooms_left 0 means full, and cancellation is the hotel's refund rule. It does not cover auth, rate limits, or pagination, so it stops short of a full 5.

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?

Purpose and date scope are front-loaded in the first sentence, followed by field semantics in short, dense clauses. Every line carries information, though the parenthetical about guest count and multi-room groups is packed enough to need a second read.

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?

With no output schema, the description correctly takes on return-value explanation (price_toman, rooms_left, cancellation, meals) and the empty-list edge case, which is what an agent needs to interpret results. It is nearly complete for a 4-parameter read tool; only structural details of the rooms list itself are absent.

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, but the description adds real meaning beyond the schema by clarifying that guest count does not affect price and that guests instead selects rooms whose capacity fits ('choose rooms whose sleeps fits'). The date-range parameter semantics (1-30 nights) remain schema-only.

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 description gives a specific resource and scope: 'Every room of a hotel with its exact price for the dates', plus the fields returned (whole stay, per night, rooms left, meals). It partially differentiates from siblings by routing empty results to mb_hotel_calendar, but never states how it differs from mb_hotel or mb_search_hotels, which an agent must infer.

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 a clear use condition (fetch room-level availability and prices for a hotel/date range) and an explicit fallback with its trigger: 'Empty rooms list = nothing free for these dates (try mb_hotel_calendar)'. Prerequisites are only implied through the schema's reference to mb_search_hotels/mb_city_hotels for the hotel slug.

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

Deploy Server

Other Tools