Skip to main content
Glama

Flat Flights — business & first class fares

Cheapest business class departure cities to a destination

cheapest_business_class_to
Read-only

Departure cities ranked by cheapest round-trip business class fare to a destination. Use for "cheapest place to fly business class to X from".

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": {
      "to": "<to>"
    },
    "name": "cheapest_business_class_to"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesCity name (e.g. "Milan", "New York") or 3-letter IATA city/airport code (e.g. "MIL", "JFK").
limitNo

Output Schema

NameRequiredDescriptionDefault
cityYes
pageYes
routesYes
fetchedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds the meaningful semantic detail that fares are round-trip, but says nothing about currency, fare freshness/caching, or coverage of origins, which matters for an open-world fare lookup.

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?

Two sentences, zero filler, with the ranking behavior front-loaded and the usage cue second. Nothing is repeated from the title or schema verbatim.

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

Completeness4/5

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

An output schema exists, so return-value explanation is unnecessary, and with only one required parameter the description carries enough for correct invocation. The remaining gaps (fare freshness, currency, the undocumented 'limit') are modest rather than blocking.

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 50%: the 'to' parameter is fully documented in the schema, but 'limit' has no description anywhere, and the description does not compensate by explaining what the limit caps (results returned vs. ranked cities). The description does reinforce that 'to' is the destination, adding marginal meaning.

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 and resource: ranks departure cities by cheapest round-trip business class fare to a destination. The directionality (cities → destination) is unambiguous, though it never contrasts itself with the sibling cheapest_business_class_from, which is the inverse query and the most likely confusion.

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?

Embeds a quoted example query ("cheapest place to fly business class to X from") that implicitly signals when to reach for it, which is useful intent matching. However, it gives no explicit exclusions, no mention of the inverse-direction sibling, and no prerequisites such as whether fares are live or cached.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources