Skip to main content
Glama
Deal Radar MCP Server

Deal Radar MCP Server

get_flight_card_offers

Find active credit card coupons and instant flight discounts across airlines and booking portals, with optional filters by bank or provider.

Instructions

List active credit card coupons and instant discounts across airlines and booking portals (HDFC, ICICI, Axis, SBI, Amex, Kotak).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_flight_card_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault
bankNoFilter by bank name (e.g. "HDFC", "ICICI", "Axis", "Amex")
providerNoFilter by provider (e.g. "EaseMyTrip", "MakeMyTrip", "IndiGo Direct")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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. 'List' clearly implies a read-only, non-mutating operation and 'active' signals that expired coupons are filtered out, which is useful context. However, it says nothing about result volume, pagination, caching, or whether zero-match searches return an empty list or an error.

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-front-loaded sentence with the verb and resource leading and scope qualifiers trailing; nothing is padded. The bank-name parenthetical partly duplicates the schema's own examples, which is the only minor waste.

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?

This is a simple two-optional-parameter read tool, and the description adequately conveys what it returns at a high level. Since no output schema exists, the description would ideally sketch what an 'offer' contains (discount amount, coupon code, eligibility), which it leaves entirely unspecified.

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 both optional filters are already documented with examples in the schema. The description repeats the bank names (HDFC, ICICI, Axis, SBI, Amex, Kotak) and portals without adding syntax, matching behavior, or combination semantics such as how bank and provider filters interact.

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 ('List') and resource ('active credit card coupons and instant discounts') scoped to airlines and booking portals, with named banks. An agent can tell this is a discovery/listing tool rather than a calculation tool, though the description never names the sibling it contrasts with (calculate_flight_card_discount).

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?

There is no explicit when-to-use, when-not-to-use, or alternative-tool guidance. 'Active' implies results are limited to currently valid offers, but nothing tells the agent whether to call this before calculate_flight_card_discount, or how it relates to search_flights or search_deals.

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