Deal Radar MCP Server

search_flights

Compare flights across airlines and travel portals, then calculate exact final prices including fees, coupons, and card discounts to reveal the true cost.

Instructions

SkyScanner-style Flight Deal Radar: Search and compare flights across direct airline websites (IndiGo, Air India, Akasa Air, SpiceJet) and travel portals (EaseMyTrip, MakeMyTrip, Cleartrip, Ixigo). Computes exact final prices including convenience fees, coupons, and credit card instant discounts.

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>"
    },
    "name": "search_flights"
  }
}

Input Schema

Name	Required	Description
`origin`	Yes	Departure airport IATA code or city name (e.g. "DEL", "BOM", "BLR", "VNS", "New Delhi", "Varanasi")
`sortBy`	No	SkyScanner sort criteria: "cheapest" (lowest net price), "fastest" (shortest duration), or "best" (optimal balance)
`userCards`	No	Credit/Debit card banks you have to unlock exclusive instant discounts (e.g. ["HDFC", "ICICI", "Axis", "SBI", "Amex", "Kotak", "Federal"])
`cabinClass`	No	Cabin class (default: "economy")
`directOnly`	No	Filter for non-stop direct flights only
`passengers`	No	Number of passengers (default: 1)
`destination`	Yes	Arrival airport IATA code or city name (e.g. "BOM", "BLR", "GOI", "Mumbai", "Goa")
`departureDate`	No	Departure date in YYYY-MM-DD format (defaults to 3 days from now)
`departureTimeWindow`	No	Time-of-day departure filter: "early_morning" (00:00-06:00), "morning" (06:00-12:00), "afternoon" (12:00-18:00), or "evening" (18:00-24:00)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It usefully discloses that results include computed final prices with convenience fees, coupons, and instant card discounts, which is real behavioral context. However, it says nothing about live network fetching from external sites, typical latency, result volume, side effects, or whether any booking action could occur.

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?

Two sentences, front-loaded with the core capability, with no filler or repetition. The 'SkyScanner-style Flight Deal Radar' branding is slightly promotional but still communicates the comparison model efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter tool with no annotations and no output schema, the definition covers what the tool does but not what comes back: no mention of result shape, currency, number of options, or whether booking links are included. That leaves an agent able to call it but uncertain how to consume the response.

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 enums for sortBy, cabinClass, and departureTimeWindow, is already fully documented. The description adds no parameter-level detail beyond schema (e.g., how userCards interacts with price computation), so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb+resource ('Search and compare flights') and names the exact provider set (airlines and travel portals), plus the distinctive value-add of computing final prices with fees and card discounts. It does not state how it differs from siblings like compare_prices or search_deals, so it lands short of a 5.

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?

Usage is only implied: the framing as an aggregating search over many providers suggests it is the entry point for broad flight lookups, but there is no explicit 'use this when' or 'use X instead for Y' statement. The point vs get_flight_card_offers, compare_prices, or search_deals is left for the agent to infer.

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