Skip to main content
Glama
negm17111995

MAQAMI Travel

by negm17111995
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Get flight booking extras

get_flights_bookings_bookingid_services
Read-onlyIdempotent

Overview

Instructions

Overview

Retrieve the ancillary services (seats, baggage) for an existing flight booking: services that are already booked together with the live catalog of services that can still be booked.

When to Use

  • Post-booking upsell - Show the passenger which seats and bags they can still add after the booking was created

  • Booking management - Display the services already attached to the booking with the prices that were charged

  • Availability refresh - The bookable catalog is fetched live from the provider on every call

What You Get

  • groups - Bookable services grouped by category (seat, baggage) with post-margin prices and encoded serviceIds

  • bookedServices - Services already attached to the booking; entries booked through the API carry the exact price that was charged at attach time

  • expiresAt - Validity window of the bookable catalog

Key Features

  • Read-only: Safe to call at any time; the catalog reflects live availability

  • Consistent pricing: Booked services echo the post-margin amounts the user actually paid

Quick Start

Provide the bookingId from the flight booking confirmation.

On a ticketed booking (status CONFIRMED) groups lists only what can be sold after ticketing (provider-dependent, usually baggage) and only when canAddServicesAfterTicketing is true; buy them with POST /flights/bookings/{bookingId}/services and /services/confirm.

Requires the bookingId and the email used to book: the server only returns or changes a booking when they match.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYesThe email address used to make the booking. The server checks it against the booking before returning or changing anything.
lastNameNoThe booking holder's last name, if the customer gives it. Optional.
bookingIdYesThe unique booking identifier
forceRefreshNoBypass the provider's 15-minute services cache
includeServicesHistoryNoInclude non-confirmed bookedServices rows (pending, requested, failed, replaced, dropped). By default only confirmed rows are returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.10
    • addedInput schema / properties / forceRefresh
      Added value: +{
+  "description": "Bypass the provider's 15-minute services cache",
+  "type": "boolean"
+}
    • addedInput schema / properties / includeServicesHistory
      Added value: +{
+  "description": "Include non-confirmed bookedServices rows (pending, requested, failed, replaced, dropped). By default only confirmed rows are returned.",
+  "type": "boolean"
+}
  2. Changed3 schema fields changedv1.0.6
    • addedInput schema / properties / email
      Added value: +{
+  "description": "The email address used to make the booking. The server checks it against the booking before returning or changing anything.",
+  "type": "string"
+}
    • addedInput schema / properties / lastName
      Added value: +{
+  "description": "The booking holder's last name, if the customer gives it. Optional.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "bookingId"
-]New value: +[
+  "bookingId",
+  "email"
+]
  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 cover readOnly/idempotent/openWorld/non-destructive, but the description adds real value: the catalog is fetched live on each call, booked-via-API entries echo the exact post-margin price paid, expiresAt bounds catalog validity, and ticketed CONFIRMED bookings behave differently (gated by canAddServicesAfterTicketing). It does not cover pagination or error/auth-failure behavior, so not a full 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Markdown headers front-load the overview and usage before details, which aids scanning. It is on the verbose side with some repetition of the read-only/pricing points across sections, but no section is purely filler.

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 carries the return-shape burden and does so well, enumerating groups, bookedServices, and expiresAt, plus the ticketing conditional that affects what groups contains. An agent has everything needed to call and interpret it.

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 the schema already documents all five parameters including forceRefresh and includeServicesHistory. The description only restates the bookingId/email matching requirement, adding little syntax or format detail beyond the structured fields — 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 (retrieve) and resource (ancillary services for a flight booking), and clarifies the dual scope: already-booked services plus the live bookable catalog. This cleanly distinguishes it from the sibling get_flights_bookings_bookingid, which returns the booking itself.

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?

An explicit 'When to Use' section lists three concrete scenarios (post-booking upsell, booking management, availability refresh), and the Quick Start names the required bookingId/email and the companion write endpoints to buy services. Alternatives and conditions are spelled out rather than implied.

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