Skip to main content
Glama
sepehr071

mrbilit-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Flight fare details

mb_flight_fare_details
Read-onlyIdempotent

Retrieve every fare for a flight with refund penalties, baggage allowance, fare rules and per-passenger prices. Re-runs the flight search to confirm airline baggage and refund terms before booking.

Instructions

Every fare of one flight with refund penalties, confirmed baggage, fare rules, notes and per-passenger prices.

Re-runs the mb_search_flights search (same route, date, party). baggage_checked_with_airline true = re-checked with the airline (false = search value, usually right). refund_penalties: penalty percent per window before departure, refund = paid x (100 - penalty_pct) / 100; penalty_text when there is no percent.

Input Schema

NameRequiredDescriptionDefault
dateYesGregorian date YYYY-MM-DD, e.g. '2026-10-20'.
adultsNoAdults (12+).
originYesIATA airport or city code from mb_find_place(mode='flight'), e.g. 'THR', 'MHD', 'IKA' or 'ISTALL' (all Istanbul airports).
infantsNoInfants (under 2).
childrenNoChildren (2-11).
flight_idYesflight_id from mb_search_flights, e.g. '21919377' (international round trip: '21894997+21924108').
full_textNoReturn long texts uncut instead of clipped.
destinationYesIATA airport or city code from mb_find_place(mode='flight'), e.g. 'THR', 'MHD', 'IKA' or 'ISTALL' (all Istanbul airports).
return_dateNoOnly for an international round-trip package: its return date YYYY-MM-DD, e.g. '2026-10-23'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv0.3.0
    • removedInput schema / properties / adults / title
      Removed value: -"Adults"
    • removedInput schema / properties / children / title
      Removed value: -"Children"
    • removedInput schema / properties / date / title
      Removed value: -"Date"
    • removedInput schema / properties / destination / title
      Removed value: -"Destination"
    • removedInput schema / properties / flight_id / title
      Removed value: -"Flight Id"
    • addedInput schema / properties / full_text
      Added value: +{
+  "default": false,
+  "description": "Return long texts uncut instead of clipped.",
+  "type": "boolean"
+}
    • removedInput schema / properties / infants / title
      Removed value: -"Infants"
    • removedInput schema / properties / origin / title
      Removed value: -"Origin"
    • removedInput schema / properties / return_date / title
      Removed value: -"Return Date"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "mb_flight_fare_detailsDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: the call re-executes a full search (implying latency/cost), and it explains how to interpret the returned baggage_checked_with_airline flag and the refund penalty formula. It omits any note on rate limits or result size/pagination.

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 tight blocks: the first sentence front-loads what the tool returns, the second covers the re-run behavior and the two non-obvious output fields. No filler or restated title text.

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 must carry return-value meaning, and it does so for the two fields most likely to be misread (baggage_checked_with_airline, refund_penalties). Other returned data (fare rules, notes, per-passenger price structure) is named but not explained, which is a minor gap for a 9-parameter read tool with full schema coverage.

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 every parameter (including the 'ALL' city-code pattern and flight_id format) is already documented in the schema — the baseline is 3. The description only indirectly reinforces this by saying the search must be re-run with the same route, date and party; it adds no syntax or format detail of its own.

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?

Opens with a specific verb+resource: 'Every fare of one flight with refund penalties, confirmed baggage, fare rules, notes and per-passenger prices.' This clearly separates it from mb_search_flights (which finds flights) and mb_flight_price_calendar (which shows price trends) without needing to open any schema.

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?

'Re-runs the mb_search_flights search (same route, date, party)' tells the agent the prerequisite (a prior search producing flight_id) and that the route/date/party inputs must match that search. It does not explicitly state when to prefer mb_flight_price_calendar or other siblings, so it stops short of full routing guidance.

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