Skip to main content
Glama

Server Details

Cheapest observed fare, 6-month low and best departure date for a city pair.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
dagrang-repository/aplusz
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A4.2/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct role: find_cheapest_fare handles a specific origin-destination pair, list_routes_from provides destination discovery, and resolve_city is a pure lookup helper. The descriptions explicitly state when to use each and even clarify directional/per-pair semantics, leaving no realistic misselection.

Naming Consistency5/5

All three names follow the same predictable snake_case verb_noun pattern (find_cheapest_fare, list_routes_from, resolve_city) with clear, action-oriented verbs. No mixing of conventions or vague names.

Tool Count4/5

Three tools is on the lean side, but each earns its place: a lookup, a discovery query, and a resolver that the other tools depend on. It is well-scoped for a narrow fare-snapshot domain, though a fourth tool (e.g. reverse or date-search) would not feel redundant.

Completeness3/5

Core workflows (resolve a city, price one pair, explore from an origin) are covered, but notable gaps exist: there is no route lookup into a destination, no date/period flexibility, and the referenced live_check_url is a data field rather than a callable tool. Agents can work around these but will hit dead ends for some fare questions.

Available Tools

3 tools
find_cheapest_fareCheapest fare between two citiesAInspect

Returns the cheapest observed one-way fare between two cities, plus the six-month low and the departure date on which the low was observed. Use whenever the user names an origin and a destination and asks about price, the cheapest date to fly, or whether a fare is a good deal. Both arguments are required; neither alone produces a valid answer. Answers are directional and per pair - PAR to BKK is not BKK to PAR and is not PAR to SIN. Prices are cached snapshots, never live quotes: say "last observed", never "current price", and surface live_check_url to any user about to book.

Inputs: to (required), from (required).

list_routes_fromCheapest destinations from one cityAInspect

Returns destinations reachable from one origin, sorted cheapest first. Use when the user asks where they can fly cheaply from a city, or wants inspiration rather than one specific pair. One call replaces dozens of page fetches. Prices are cached snapshots.

Inputs: from (required), limit.

resolve_cityResolve a city name to its IATA codeAInspect

Turns a spoken city name into the uppercase IATA city code the other tools expect. Call this before find_cheapest_fare whenever you are not certain of a code. Do not invent codes.

Inputs: query (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables real-time flight fare searches across date ranges and multiple destinations, with historical price insights and booking links. Provides one-way and round-trip search tools through MCP.
      4
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables users to find the cheapest dates to fly a route via Google Flights, supporting one-way and round-trip searches through multiple backends. It provides a tool that can search date ranges, filter by nonstop, seat, currency, and force a particular backend.
      1
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.