Skip to main content
Glama

Flight fare details

mb_flight_fare_details
Read-onlyIdempotent

Retrieve complete fare details for a chosen flight—refund penalties, baggage allowance, fare rules, notes and per-passenger prices—to compare costs and booking conditions.

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). refund_penalties: penalty percent per window before departure, refund = paid x (100 - penalty_pct) / 100.

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": {
      "origin": "<origin>",
      "destination": "<destination>",
      "date": "<date>",
      "flight_id": "<flight_id>"
    },
    "name": "mb_flight_fare_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesGregorian date YYYY-MM-DD.
adultsNoAdults (12+).
originYesIATA airport or city code from mb_find_place(mode='flight'), e.g. 'THR', 'MHD', 'ISTALL' (all Istanbul airports).
infantsNoInfants (under 2).
childrenNoChildren (2-11).
flight_idYesflight_id from mb_search_flights, e.g. '21919377' or '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', 'ISTALL' (all Istanbul airports).
return_dateNoReturn date, only for an international round-trip package.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.5.0
    • changedInput schema / properties / date / description
      Previous value: -"Gregorian date YYYY-MM-DD, e.g. '2026-10-20'."New value: +"Gregorian date YYYY-MM-DD."
    • changedInput schema / properties / destination / description
      Previous value: -"IATA airport or city code from mb_find_place(mode='flight'), e.g. 'THR', 'MHD', 'IKA' or 'ISTALL' (all Istanbul airports)."New value: +"IATA airport or city code from mb_find_place(mode='flight'), e.g. 'THR', 'MHD', 'ISTALL' (all Istanbul airports)."
    • changedInput schema / properties / flight_id / description
      Previous value: -"flight_id from mb_search_flights, e.g. '21919377' (international round trip: '21894997+21924108')."New value: +"flight_id from mb_search_flights, e.g. '21919377' or '21894997+21924108'."
    • changedInput schema / properties / origin / description
      Previous value: -"IATA airport or city code from mb_find_place(mode='flight'), e.g. 'THR', 'MHD', 'IKA' or 'ISTALL' (all Istanbul airports)."New value: +"IATA airport or city code from mb_find_place(mode='flight'), e.g. 'THR', 'MHD', 'ISTALL' (all Istanbul airports)."
    • removedInput schema / properties / return_date / anyOf
      Removed value: -[
      -  {
      -    "format": "date",
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / return_date / description
      Previous value: -"Only for an international round-trip package: its return date YYYY-MM-DD, e.g. '2026-10-23'."New value: +"Return date, only for an international round-trip package."
    • addedInput schema / properties / return_date / format
      Added value: +"date"
    • addedInput schema / properties / return_date / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / title
      Removed value: -"mb_flight_fare_detailsArguments"
  2. 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
  3. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds behavior beyond that: the call re-executes the underlying search (implying cost/latency and that results can shift between calls) and it explains how refund penalties are computed, which is not derivable from annotations.

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 short sentences, front-loaded with what you get and followed by the invocation constraint and the penalty formula. No filler or restatement of the name.

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 9 parameters, no output schema and an open-world dependency, the description does the needed work by enumerating the returned fare components and the refund math. Slightly short of full completeness since it says nothing about failure modes when the flight_id is stale or sold out.

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 description coverage is 100%, so baseline is 3. The description adds a real constraint the schema does not encode: origin, date and passenger counts must mirror the original search ('same route, date, party'), which affects whether the flight_id resolves. It explains the refund_penalties meaning too, though that is a return field rather than a parameter.

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: 'Every fare of one flight' with the concrete payload (refund penalties, confirmed baggage, fare rules, notes, per-passenger prices). It also distinguishes itself from the sibling it depends on by noting it 'Re-runs the mb_search_flights search', making clear this is the per-flight fare drill-down rather than the search itself.

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?

Gives clear context for use: it must be invoked with the same route, date and party as the original mb_search_flights call, and flight_id comes from that search. It does not state when to prefer alternatives such as mb_flight_price_calendar or what to do if the flight is no longer available, so no explicit exclusions.

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