Deal Radar MCP Server

set_flight_price_alert

Monitor a specific flight route's live fare and send a notification when the price falls below your target threshold.

Instructions

Set an autonomous price drop alert for a specific flight route. Deal Radar will monitor live fares and notify you when the route price drops below your target threshold.

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

Input Schema

Name	Required	Description
`notes`	No	Optional user note for this flight alert
`origin`	Yes	Departure airport code or city (e.g. "DEL", "VNS")
`cabinClass`	No	Cabin class (default: economy)
`destination`	Yes	Arrival airport code or city (e.g. "BOM", "BLR")
`targetPrice`	Yes	Target price in ₹ to trigger notification (e.g. 3500)
`departureDate`	No	Optional departure date in YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses autonomous monitoring and threshold-based notification, but it does not explain permissions, alert persistence, notification frequency, how to remove the alert, or what confirmation is returned.

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?

The description is two sentences, front-loaded with the core action and followed by the monitoring behavior. There is no redundant or filler wording.

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?

The description is adequate for a creation tool with a fully documented input schema, but it lacks details about the alert lifecycle, return value, and management path. With no annotations and no output schema, those omissions leave some operational context unstated.

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 input schema already documents all six parameters, including origin, destination, targetPrice, cabinClass, departureDate, and notes. The description adds only the general concept of a target threshold and does not add parameter-specific meaning beyond the schema.

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?

The description states a specific verb and resource: "Set an autonomous price drop alert for a specific flight route." It also clarifies the mechanism, monitoring live fares and notifying below a target threshold, which helps distinguish it from a generic price alert, though it does not explicitly name sibling alternatives.

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?

The description implies the tool is used to create a flight-route price alert, but it gives no explicit when-to-use guidance, no when-not-to-use conditions, and no comparison to alternatives such as set_price_alert or other alert-management tools.

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