MAQAMI Travel

by io.github.negm17111995

Confirm flight price and get checkout link

post_flights_verify

Read-only

Overview

Confirm a flight offer is still available and retrieve the latest pricing before proceeding to booking. Returns the checkout link for the verified offer.

When to Use

Pre-booking validation - Confirm offer availability after user selects a flight
Price confirmation - Show users the guaranteed price
Fare rule retrieval - Get the latest cancellation and change policies

What You Get

Verified pricing with up-to-date fare breakdown
changes (when present) — cabin/fare flags, human-readable messages, and pricing (old / new full OfferPricing) instead of deprecated scalar currency/prices
Journey pricing — original (provider/PCC) and display (customer) price breakdown per provider FlattenedJourney
Fare family details including name and included amenities
Baggage policy for each passenger type and segment
Booking terms including cancellation and change fee rules

Key Features

Real-time price check: Confirms current availability and price with the provider
Updated baggage info: Returns the latest baggage allowances at time of verification
Fare rules: Includes cancellation and change fee policies before commitment

Quick Start

Provide the offerId from post_flights_rates search results. The verified offer data gives the customer a booking summary.

Booking

The response includes checkoutUrl (https://book.maqami.co/flights/booking?offerId=...). Flights are booked and paid only on MAQAMI's website: the checkoutUrl opens checkout for this fare, where the customer enters passenger details, pays securely and receives the confirmation. This tool takes no card or passport details.

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": {
      "offerId": "<offerId>"
    },
    "name": "post_flights_verify"
  }
}

Input Schema

Name	Required	Description	Default
`offerId`	Yes	The offerId from the search results
`sessionId`	No	Optional journey session id. Send your own to group the calls of one journey: up to 64 visible ASCII characters without spaces (a value outside these limits is ignored, the call still succeeds). When omitted on rates, MAQAMI creates one and returns it. Every offer remembers the session of its search, so verify and prebook continue it when you do not resend it; on book, an omitted value inherits the session of the prebook.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 13, 2026

addedInput schema / properties / sessionId

Added value: +{
+  "description": "Optional journey session id. Send your own to group the calls of one journey: up to 64 visible ASCII characters without spaces (a value outside these limits is ignored, the call still succeeds). When omitted on rates, MAQAMI creates one and returns it. Every offer remembers the session of its search, so verify and prebook continue it when you do not resend it; on book, an omitted value inherits the session of the prebook.",
+  "type": "string"
+}

First observedOct 4, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly=true, openWorld=true and non-idempotent; the description adds real value beyond them by disclosing that a live provider re-check happens ('Confirms current availability and price with the provider'), that no card or passport details are taken, and that payment occurs off-tool at checkoutUrl. It does not warn about rate limits or repeated-call cost, which is a minor gap for a non-idempotent live check.

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 headings and front-loaded Overview make it easy to scan, and the return-value detail earns its place because there is no output schema. However, 'Key Features' largely restates 'When to Use' and 'What You Get' (fare rules, baggage, real-time price check appear twice), so some trimming is warranted.

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?

No output schema exists, so the description carries the return contract itself, and it does so thoroughly: changes/pricing objects, journey original vs display pricing, fare family, baggage, booking terms and the checkoutUrl format. An agent has everything needed to call and interpret the result.

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% and both parameters are fully documented in the schema, so the baseline is 3. The description adds only the provenance hint that the offerId comes from post_flights_rates search results; sessionId is not discussed in the description at all.

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 Overview states a specific verb and resource: confirm an offer is still available, refresh pricing, and return a checkout link. The 'When to Use' bullets ('Pre-booking validation - Confirm offer availability after user selects a flight') clearly separate it from the sibling post_flights_rates search step.

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?

It gives explicit triggering conditions (pre-booking validation, price confirmation, fare rule retrieval) and ties itself to the search step by telling the agent to supply the offerId from post_flights_rates results. It never states exclusions or alternatives in a 'when not to use' form, so it falls just short of the top score.

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

All MAQAMI Travel tools Inspect

Try in Browser