Skip to main content
Glama

Server Details

Flying club and aircraft partnership management — book your aircraft, check availability, log Hobbs/Tacho hours, settle flights and pull METAR from your AI assistant.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 17 tools

Disambiguation4/5

Most tools have distinct roles, especially across booking, availability, and settlement workflows. Minor potential confusion exists between get_aircraft_availability and find_available_slots, and among get_aircraft_hours, get_flight_statistics, and get_pilot_activity, but descriptions clarify the boundaries.

Naming Consistency5/5

All tools use snake_case with a predictable verb_noun pattern such as create_booking, cancel_booking, get_my_bookings, and settle_booking. Longer names like get_dispatch_context_and_time and get_booking_settlement_info remain readable and consistent with the convention.

Tool Count4/5

At 17 tools, the surface is slightly above the typical 3-15 range but still reasonable for a flight-club workflow spanning bookings, dispatch, settlement, weather, maintenance, and statistics. Each tool appears to support a distinct operational step rather than duplicating another.

Completeness4/5

Core booking, dispatch, settlement, weather, and aircraft-state workflows are covered, including create/cancel booking and preview/finalize settlement. Minor gaps exist, such as no explicit update/reschedule booking tool or single-booking detail tool, but agents can likely work around these with existing tools.

Publisher details

Operator
Pilot-Next · Publisher source
Vendor relationship
Not applicable
Privacy policy
Not provided
Trust center
Not available
Restrictions
You need a Pilot-Next account - SOLO Free Forever - BASIC €9.00 per month (billed annually) - PRO €18.00 per month (billed annually) - ULTRA €45.00 per month (billed annually) · Publisher source

Available Tools

17 tools
cancel_bookingAInspect

Cancel a booking. A pilot can cancel only their own bookings; an admin can cancel any booking in the club. ULTRA-PROACTIVE: If the user says "cancel my booking", use "get_my_bookings" to find the ID, OR use the [INTERNAL_ID] from a previous create_booking success message. NEVER ask the user for an ID you can find yourself.

Inputs: bookingId (required).

create_bookingAInspect

Create a booking. CRITICAL: Check start/end time year. Do NOT default to 2024. Use 'get_dispatch_context_and_time' to verify "Today". ONE-SHOT: CALCULATE dates yourself from context. Do NOT ask user for ISO strings. ACTION: You MUST output the Booking Confirmation Summary returned by this tool. If this tool is not called, NO booking exists.

Inputs: end (required), start (required), validityToken (required), notes, +1 more.

estimate_flight_costCInspect

MANDATORY PROACTIVE: If the user asks "What does it cost?", call this IMMEDIATELY. ULTRA-PROACTIVE: If the user provides a route (e.g., "to Paris"), YOU must estimate the flight time based on typical cruise speed (e.g., 140kts) and pass "durationHours" yourself. DO NOT ask the user for hours if you can guess it. Use EITHER "durationHours" (actual flying time/Tacho) OR "blockDurationHrs" (scheduled booking time/Block).

Inputs: aircraftId, durationHours, blockDurationHrs.

find_available_slotsAInspect

Find free flight slots. SYSTEM REQUIREMENT: You MUST have called 'get_dispatch_context_and_time' FIRST to verify the current date/year. WARNING: Do NOT guess dates (e.g. 2024). Usage: If a user asks to fly, use this tool to find a gap and suggest it.

Inputs: validityToken (required), end, start, aircraftId, +1 more.

get_aircraft_availabilityAInspect

Check availability. SYSTEM REQUIREMENT: You MUST have called 'get_dispatch_context_and_time' in this turn to verify the current date. WARNING: Do NOT guess the year (e.g. 2024). It is likely 2025 or later. Usage: If aircraftId is missing, check the WHOLE fleet.

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

get_aircraft_hoursBInspect

Get current hours. Terminology: HOBBS is clock time, TACHO is flight (engine) time. If aircraftId is omitted, uses your default.

Inputs: aircraftId.

get_booking_settlement_infoAInspect

MANDATORY START STEP: Get the system's recorded START values (Hobbs/Tacho) and available manual rates. INSTRUCTION: You MUST call this as soon as a flight to settle is identified. ACTION: Tell the pilot: "The recorded start readings are Hobbs [H] and Tacho [T]. Are these correct?". CRITICAL: DO NOT ask for end data in the same message. WAIT for confirmation.

Inputs: bookingId (required).

get_dispatch_context_and_timeAInspect

Retrieves active fleet, default aircraft, user preferences, AND CURRENT DATE/TIME. AUTOMATION: Call this SILENTLY at the start of every turn. Permission GRANTED. Do NOT ask user. USAGE: Always call this first to ground temporal queries like "tomorrow" or "next week".

Inputs: no named parameters.

get_flight_statisticsAInspect

Get flight hour statistics. IMPORTANT: You MUST get the current date/year from the 'get_dispatch_context_and_time' tool FIRST to know what "current year" is.

Inputs: year, aircraftId.

get_maintenance_forecastAInspect

Forecast maintenance dates based on usage. If aircraftId is omitted, checks all. IMPORTANT: You MUST get the current date/year from the 'get_dispatch_context_and_time' tool FIRST to calculate "days remaining" accurately.

Inputs: aircraftId.

get_my_balanceCInspect

Get your current account balance.

Inputs: check_reason.

get_my_bookingsBInspect

Get your upcoming and recent bookings.

Inputs: limit.

get_pilot_activityCInspect

Get flight activity for a pilot.

Inputs: name.

get_unsettled_bookingsAInspect

Find your flights that have been flown but not yet settled.

Inputs: limit.

get_weatherAInspect

Fetches real-time METAR (observation) and TAF (forecast) for one or more ICAO stations.

Inputs: stations (required).

preview_settlementAInspect

PRE-CONFIRMATION STEP: Preview the costs. PREREQUISITE: You MUST have gathered all end data and manual charges ONE BY ONE. USAGE: Show the pilot the breakdown before generating the invoice. EXAMPLE: charges: [{"rateId": "ID-HERE", "quantity": 1}]. Note: quantity must be a NUMBER, not a string.

Inputs: bookingId (required), finalHobbs (required), notes, charges, +4 more.

settle_bookingAInspect

FINAL STEP: Finalize the settlement and generate the invoice. PREREQUISITE: You MUST have called 'preview_settlement' and received explicit confirmation (e.g. "yes") from the pilot FIRST. CRITICAL: DO NOT call this if the pilot has not seen and confirmed the costs in the preview.

Inputs: bookingId (required), finalHobbs (required), notes, charges, +4 more.

Tool Schema Changelog

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

Loading tool schema changelog…

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Remote MCP server that lets AI assistants read tracked competitive intelligence — competitor news, reviews, website changes, social posts and ads — and act on it by managing projects, competitors, battle cards, reports and canvases. Every answer carries a source and a date, and write actions only publish when explicitly shared.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.
      16
      9 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Browse IndustryLens's published competitive-intelligence reports and head-to-head competitor comparisons from any AI agent — real, source-backed data.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources