Skip to main content
Glama
Deal Radar MCP Server

Deal Radar MCP Server

analyze_fare_bucket_state

Evaluates current fare against advance-purchase cliffs, route price quantiles, and GDS buckets to recommend BUY_NOW, WAIT_FOR_SWEEP, or HOLD_FARE with confidence and price-floor estimate.

Instructions

Flight Price Prediction & Decision Engine: Evaluates current fare against Advance Purchase (AP) cliffs (21d, 14d, 7d), historical route quantiles (p10, p25, p50), and GDS bucket inventory, recommending BUY_NOW, WAIT_FOR_SWEEP, or HOLD_FARE with confidence score and predicted price floor.

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

Input Schema

NameRequiredDescriptionDefault
originYesOrigin airport or city (e.g. "IDR", "DEL")
cabinClassNoCabin class
destinationYesDestination airport or city (e.g. "BLR", "BOM")
currentPriceNoCurrent observed price in ₹
flightNumberNoOptional flight number (e.g. "6E-1117")
departureDateNoDeparture date in YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It helpfully reveals the output shape (recommendation enum, confidence score, predicted price floor), but never states that this is a read-only analytical operation with no side effects, nor how behavior degrades when optional inputs like currentPrice or departureDate are omitted — a real concern given only origin/destination are required.

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?

One dense sentence, front-loaded with the tool's identity and followed by the specific signals and outputs. Jargon-heavy (AP cliffs, GDS buckets) but every clause carries information; nothing is padding.

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 six-parameter, no-annotation, no-output-schema analytical tool, the description covers purpose and output semantics well, but leaves gaps on optional-parameter behavior, data freshness (live GDS vs cached inventory), and the thresholds that drive each recommendation. An agent could call it, but could not predict results reliably.

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 coverage is 100%, so baseline applies. The description adds a little meaning by linking departureDate and currentPrice to the AP-cliff comparison, but it says nothing about how cabinClass or flightNumber influence the analysis, and never clarifies which inputs are optional or how missing ones affect the verdict.

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 analytical verb and the exact inputs it fuses (AP cliffs at 21d/14d/7d, historical route quantiles p10/p25/p50, GDS bucket inventory) plus the three named recommendation outcomes. This is unmistakably distinct from sibling tools like compare_prices or get_price_history, which return data rather than a BUY/WAIT/HOLD verdict.

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?

The decision framing implies when the tool is useful (deciding whether to book now), but there is no explicit when-to-use/when-not statement and no named alternative such as compare_prices for raw fare comparison or get_price_history for the underlying data. The agent must infer routing from the purpose text alone.

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