Skip to main content
Glama

AwardSecrets Award Availability

by com.awardsecrets

search_award_availability

Look up award (points/miles) seat availability for ONE specific flight route on ONE specific date with ONE specific airline, sourced from a contracted GDS rather than scraped. Returns the flights found with cabin and seat count.

IMPORTANT — this tool is strictly literal. Every argument takes a single concrete value: • origin / destination: exactly one 3-letter IATA airport code each. Not a city, not a list, not a region. • airline: exactly one 2-letter IATA carrier code (e.g. VS, CX, NH). Not an alliance and not a loyalty programme. • date: exactly one date, YYYY-MM-DD. Not a range and not a month.

To cover several airports, airlines or dates, CALL THIS TOOL ONCE PER COMBINATION and combine the results yourself. Award space is scarce and volatile, so an empty result for one date says nothing about another — checking several dates is normal and expected.

Interpreting the result: • seats is an availability indicator, not a guaranteed bookable count, and not a reservation. Low counts are the more precise signal; treat higher ones as less certain. Do not present any count as a firm number of seats a user can book. • cabin is one of business, first, economy or premium_economy. • An empty result means no availability was surfaced for that exact combination at that moment; it is not proof that the route never has space. • Availability changes fast. Treat every result as a point-in-time observation, not a reservation.

If the call is declined for want of an API key, say so plainly and point the user at https://awardsecrets.com/api.html — access is in limited release and keys are issued individually. Do not invent availability, and do not substitute a guess for a result you could not retrieve.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesOne departure date, YYYY-MM-DD.
cabinNoCabin to search. Defaults to business.business
originYesDeparture airport, one 3-letter IATA code (e.g. JFK).
airlineYesOne 2-letter IATA airline code (e.g. VS, CX, NH).
passengersNoNumber of seats required. Defaults to 1.
destinationYesArrival airport, one 3-letter IATA code (e.g. LHR).

TDQS

A5/5.0
Behavior5/5

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

With no annotations, the description carries full burden and does so thoroughly: it states the literal matching behavior, GDS data sourcing, seat/cabin result semantics, point-in-time volatility, empty-result caveats, API-key failure handling, and prohibition against inventing availability.

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?

All paragraphs carry necessary operational guidance; the opening sentence front-loads the purpose and the bulleted restrictions are scannable. Despite length, there is no filler or repetition of schema beyond the useful caveats.

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

Completeness5/5

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

The tool has six parameters, no output schema, and no annotations, yet the description explains the return concept ('flights found with cabin and seat count'), interprets seats/cabin, covers empty results, and addresses error handling. This makes the tool safe to invoke correctly in context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although the schema covers all parameters at 100%, the description adds real semantics: origin/destination must be exactly one IATA code not a city/list/region; airline must be a carrier code not an alliance; date must be one YYYY-MM-DD not a range/month. It also clarifies that seats is an availability indicator rather than a bookable count.

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?

The verb phrase 'Look up award (points/miles) seat availability' names a specific resource and scope (one route, one date, one airline), and the description distinguishes its data source ('contracted GDS rather than scraped'). Even with no siblings, the purpose is unambiguous.

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

Usage Guidelines5/5

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

It explicitly constrains each argument to a single concrete value and provides when-not guidance (not city/list/region, not alliance/loyalty programme, not date range/month). It gives an explicit repeat-call pattern ('CALL THIS TOOL ONCE PER COMBINATION') and normalizes empty results across dates.

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

All AwardSecrets Award Availability toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.9/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion between tools. The tool's purpose is highly specific and clearly described.

Naming Consistency5/5

The single tool name 'search_award_availability' follows a clear verb_noun pattern and is fully descriptive, with no other tools to create inconsistency.

Tool Count3/5

A single tool feels thin even for a narrow purpose like award availability lookup, but it is not outright excessive. The borderline range (1-2 tools) applies here.

Completeness5/5

The tool fully covers the stated domain of searching award availability for a specific route, date, and airline. No other operations are needed for a lookup-only service.

Resources