Skip to main content
Glama

get_flight_option_details

Retrieve detailed flight information including segments, pricing, and baggage details for a specific flight option from search results.

Instructions

Retrieve detailed information about a specific flight option from the search results. This tool provides detailed information about a flight option, including its segments, price, baggage info. It is useful for getting more granular information about a specific flight option.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
search_idYesSearch ID from the previous search_flights tool.
offer_idYesOffer ID of the flight option for which to request a booking link.

Implementation Reference

  • The primary handler function for the 'get_flight_option_details' tool, decorated with @mcp.tool which registers it. Retrieves cached search results by search_id, finds the specific proposal by offer_id using get_proposal_by_id, and returns detailed description via get_full_description. Includes inline schema via Pydantic Field descriptions.
    @mcp.tool(description="Retrieve detailed information about a specific flight option from the search results. " \
        "This tool provides detailed information about a flight option, including its segments, price, baggage info. " \
        "It is useful for getting more granular information about a specific flight option.")
    def get_flight_option_details(
        search_id: str = Field(..., description="Search ID from the previous search_flights tool."),
        offer_id: str = Field(..., description="Offer ID of the flight option for which to request a booking link."),
    ) -> Dict[str, Any]:
        """Get detailed information about a specific flight option from the search results."""
        
        batch = search_results_cache.get(search_id)
        if not batch:
            raise ToolError(f"No search results found for search_id: {search_id}. " \
                            "It may have expired after 10 minutes. " \
                            "Please perform a search first using the `search_flights` tool.")
        
        proposal = batch.get_proposal_by_id(offer_id)
        if not proposal:
            raise ToolError(f"No flight details found for offer_id: {offer_id} in search_id: {search_id}.")
        
        return proposal.get_full_description()
  • Helper method on ProposalsBatchModel to find and return the Proposal instance matching the offer_id (stored as 'sign'). Called directly from the tool handler.
    def get_proposal_by_id(self, proposal_id: str) -> Optional[Proposal]:
        for proposal in self.proposals:
            if proposal.sign == proposal_id:
                return proposal
        return None
  • Helper method on Proposal class that generates comprehensive string description of the flight option, including detailed flights, layovers, agency prices, baggage, etc. Returned directly by the tool handler.
    def get_full_description(self) -> str:
        description_parts = [self.get_short_description(include_cheapest_price=False, include_aircraft=True)]
        if self.is_charter:
            description_parts.append("* This is a charter flight.")
        description_parts.append(f"* This ticket is offered by {len(self.terms)} agencies with the following terms:")
        for term_id, terms in self.terms.items():
            agency = self.batch_ref.gates_info.get(term_id)
            if agency:
                description_parts.append(f"* Agency {agency.label} (internal agency ID: {term_id})")
            else:
                description_parts.append(f"* Agency (internal agency ID: {term_id})")
            description_parts.append(f"  * **Price:** {terms.price} {terms.currency.upper()} " \
                                     f"(in user currency: {convert_unified_price_to_user(terms.unified_price, self.batch_ref.currency)} {self.batch_ref.currency.upper()})")
            
            description_parts.append(f"  * Baggage info:")
            for segment_idx, segment in enumerate(self.segment):
                for flight_idx, flight in enumerate(segment.flight):
                    baggage = terms.flights_baggage[segment_idx][flight_idx]
    
                    handbag = terms.flights_handbags[segment_idx][flight_idx]
                    description_parts.append(f"    * Flight {flight.get_full_flight_number()}: \n" \
                                             f"      * {parse_baggage_string(baggage)} \n" \
                                             f"      * {parse_carry_on_string(handbag)}")
        if self.tags:
            description_parts.append(f"* Tags: {', '.join(self.tags)}")
        
        return "\n".join(description_parts)
  • TTLCache instance used across tools to store search results (ProposalsBatchModel) temporarily for 10 minutes, accessed by search_id in get_flight_option_details.
    search_results_cache = TTLCache(
        maxsize=10000,  # Maximum number of cached items
        ttl=10 * 60,  # Time to live for each cached item (10 minutes)
    )

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses output contents (segments, price, baggage) but does not mention side effects, prerequisites, authentication, or error conditions. The implied dependency on previous search is not emphasized.

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 sentences, no fluff. Front-loads the purpose, then lists contents. Every sentence adds value.

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?

Lacks output schema, but description mentions return fields. It provides enough context for a simple retrieval tool, though could clarify the connection to search_flights more explicitly.

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% with both parameters well-described. The description adds general context about output but not parameter-specific meaning beyond the schema.

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?

The description clearly states the verb 'retrieve' and the resource 'detailed information about a specific flight option'. It mentions included fields (segments, price, baggage info) and distinguishes from siblings like get_flight_options (likely returns list) and request_booking_link.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description says 'It is useful for getting more granular information' but does not explicitly state when to use or when not to use it relative to siblings. There is no mention of prerequisites or alternatives.

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