Skip to main content
Glama
Sign In
mrbilit-mcp

mrbilit-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Flight price calendar

mb_flight_price_calendar
Read-onlyIdempotent

Retrieve one-adult fare minimums per day for a route across a date range to find low-cost travel days, then search flights for the chosen date.

Instructions

Cheapest one-adult fare per day for a route over a date range, in one call.

Use to find the cheapest day to fly, then call mb_search_flights for that day. The values are the site's cached minimums and can differ from a live search; days with no known fare are left out (no flights, sold out or not cached).

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of days to cover.
originYesIATA airport or city code from mb_find_place(mode='flight'), e.g. 'THR', 'MHD', 'IKA' or 'ISTALL' (all Istanbul airports).
start_dateNoFirst day YYYY-MM-DD, e.g. '2026-10-15'; default today.
destinationYesIATA airport or city code from mb_find_place(mode='flight'), e.g. 'THR', 'MHD', 'IKA' or 'ISTALL' (all Istanbul airports).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.0
    • removedInput schema / properties / days / title
      Removed value: -"Days"
    • removedInput schema / properties / destination / title
      Removed value: -"Destination"
    • removedInput schema / properties / origin / title
      Removed value: -"Origin"
    • removedInput schema / properties / start_date / title
      Removed value: -"Start Date"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "mb_flight_price_calendarDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses that values are the site's cached minimums and may diverge from a live search, and that days with no known fare are omitted for three distinct reasons (no flights, sold out, not cached). That is exactly the caveat an agent needs before trusting the numbers.

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 short sentences, zero filler. The purpose and the headline caveat (cached, not live) are front-loaded, with the omission rule last where it belongs.

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?

There is no output schema, so the description carries the burden of explaining returns – and it does: one value per day, cheapest one-adult fare, days missing when unavailable. Nothing an agent needs to interpret or act on the result is absent.

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% – origin, destination, days and start_date are all documented with patterns, defaults and formats in the schema. The description adds only that the fare basis is one adult, which is result semantics rather than parameter guidance, 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+granularity: 'Cheapest one-adult fare per day for a route over a date range, in one call.' That immediately distinguishes it from the sibling mb_search_flights, which returns live itineraries rather than per-day minimums.

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 routes the agent: 'Use to find the cheapest day to fly, then call mb_search_flights for that day.' It names the follow-up tool and the condition that selects it, so the workflow is unambiguous.

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