Deal Radar MCP Server

get_flight_itinerary_links

Generate pre-filled direct flight itinerary links across flight websites and OTAs to simplify comparing and booking flights.

Instructions

Automatically generates exact, pre-filled direct itinerary landing links across ALL flight websites, OTAs, and aggregators (EaseMyTrip, MakeMyTrip, Goibibo, Yatra, Cleartrip, Ixigo, Skyscanner, Kayak, etc.).

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": "get_flight_itinerary_links"
  }
}

Input Schema

Name	Required	Description
`origin`	Yes	Departure airport code or city (e.g. "IDR", "DEL")
`cabinClass`	No	Cabin class (default: economy)
`passengers`	No	Number of passengers (default: 1)
`destination`	Yes	Arrival airport code or city (e.g. "BLR", "BOM")
`departureDate`	No	Departure date in YYYY-MM-DD (e.g. "2026-11-09")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations exist, so the description carries the full burden, yet it only says links are "generated." It omits whether links are affiliate/tracked, how many providers are returned, whether any auth or rate limits apply, and whether the links reflect live prices or just itinerary parameters.

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

Conciseness3/5

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

A single front-loaded sentence with no structural waste, but it spends words on marketing adjectives ("Automatically," "exact," "ALL") and a long OTA list rather than on information an agent needs to invoke it correctly.

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

Completeness2/5

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

With no annotations and no output schema, the description is the only place return shape could be described, yet it never says what comes back (a list of URLs with provider names?) or in what form. For a 5-parameter tool whose entire value is the returned links, that is a meaningful gap.

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 (origin, destination, dates, cabin class, passengers) is already documented with examples and defaults. The description adds no further meaning about how those inputs shape the generated links.

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?

States a specific verb and artifact: "generates ... pre-filled direct itinerary landing links" across named OTAs. This clearly distinguishes it from flight-search siblings like search_flights, though it never names an alternative directly.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no mention of alternatives. An agent cannot tell whether this should be called instead of search_flights, after a search, or as a standalone deep-link builder for a route.

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