Skip to main content
Glama
Deal Radar MCP Server

Deal Radar MCP Server

calculate_flight_card_discount

Calculates the applicable bank card discount, promo code, and exact net price for a flight booking using the provider, booking amount, and user cards.

Instructions

Calculate the maximum bank discount, promo code, and exact net price for a given flight booking amount and user cards.

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": {
      "bookingAmount": "<bookingAmount>",
      "provider": "<provider>"
    },
    "name": "calculate_flight_card_discount"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerYesBooking provider (e.g. "EaseMyTrip", "MakeMyTrip", "Cleartrip", "IndiGo Direct")
userCardsNoUser card banks (e.g. ["HDFC", "ICICI", "Axis", "SBI", "Amex"])
bookingAmountYesPublished flight booking amount (₹)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden; it signals a pure computation by saying it 'calculates' and lists what comes back (max discount, promo code, net price). It does not state that the call is side-effect-free, requires no booking/auth context, or that results apply to the given amount only.

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?

A single well-formed sentence with the outputs and inputs front-loaded and no filler. It is efficiently sized, though the 'maximum/exact' qualifiers would carry more weight if paired with a note on output shape.

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 three-parameter, no-annotation, no-output-schema tool, the definition covers purpose and inputs adequately but leaves gaps around return structure, whether multiple cards yield one best result versus a breakdown, and whether any prerequisite data is needed. A short sentence on the return shape would close the 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 all three parameters (provider, userCards, bookingAmount) already document their format and examples. The description adds only the framing that these inputs drive a max-discount/net-price calculation, which is the baseline expectation when the schema does the heavy lifting.

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 ('Calculate') and three concrete outputs (maximum bank discount, promo code, exact net price) scoped to a flight booking amount plus user cards. An agent can tell this is a price-computation tool rather than an offer-listing tool, though it never names the closest sibling (get_flight_card_offers) to sharpen the distinction.

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 phrase 'for a given flight booking amount and user cards' implies the situation in which to call it, but there is no explicit when-to-use/when-not guidance and no routing to or away from get_flight_card_offers or search_flights. Usage must be inferred from the input description.

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