Skip to main content
Glama
Sign In
mrbilit-mcp

mrbilit-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Hotel price calendar

mb_hotel_calendar
Read-onlyIdempotent

Compare one-night hotel room prices from today across up to ~48 days to find free nights, spot missing or not-yet-loaded dates, then check exact rates.

Instructions

Cheapest one-night room price per night from today, up to about 48 days (often fewer).

Use to find the cheapest or the next free nights, then mb_hotel_rooms for exact prices. Nights missing inside the range have no free room; nights after the last one listed are not loaded yet (not the same as sold out).

Input Schema

NameRequiredDescriptionDefault
hotelYesHotel as 'city_slug/hotel_slug' from mb_search_hotels, mb_city_hotels or mb_find_place, e.g. 'mashhad/enghelab'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.0
    • removedInput schema / properties / hotel / title
      Removed value: -"Hotel"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "mb_hotel_calendarDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world, so the safety profile is covered. The description nonetheless adds real behavioral context: the ~48-day horizon, that missing interior nights mean no availability, and that trailing gaps mean 'not loaded yet' rather than 'sold out' — a genuinely non-obvious distinction.

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?

Three tight sentences, front-loaded with the return semantics, then usage, then the edge-case interpretation. Every sentence carries information an agent would otherwise have to guess.

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?

With no output schema, the description correctly compensates by characterizing the result (per-night cheapest price), its range limit, and how to interpret gaps. That is exactly the missing structure an agent needs.

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 coverage is 100% and the single 'hotel' parameter is fully documented in the schema (format 'city_slug/hotel_slug', pattern, maxLength, example, and where to obtain it). The description adds no parameter-level detail, so the baseline 3 applies.

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+resource+scope: the cheapest one-night room price per night, starting today and running up to ~48 days. It is immediately distinguishable from mb_hotel_rooms (exact prices) and from the train/bus/flight calendar siblings.

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?

Explicitly says when to use it ('to find the cheapest or the next free nights') and names the follow-up tool ('then mb_hotel_rooms for exact prices') for the precision case. Nothing is left to inference about tool selection.

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