SimBrief MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SIMBRIEF_PILOT_ID | Yes | Your SimBrief Pilot ID, found under SimBrief → Account Settings → Pilot ID |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_flight_summaryA | High-level summary of a flight plan: flight number, aircraft, route, distance, cruise altitude, estimated times and total fuel. Leave plan_id empty to get the latest dispatch. |
| get_weatherB | Current weather: METAR, TAF and ATIS for departure, arrival and alternate airports. Leave plan_id empty to get the latest dispatch. |
| get_fuel_planA | Detailed fuel breakdown: taxi, trip burn, contingency, alternate burn, reserve, minimum and planned takeoff fuel, plus any extra fuel buckets. Leave plan_id empty to get the latest dispatch. |
| get_weightsA | Aircraft weight breakdown: OEW, payload, passenger count, ZFW, TOW, ramp weight and landing weight. Leave plan_id empty to get the latest dispatch. |
| get_timesA | All flight times in UTC: scheduled OUT/OFF/ON/IN, estimated time enroute, block time, taxi times, reserve and endurance. Leave plan_id empty to get the latest dispatch. |
| get_atc_flightplanA | ATC flight plan string ready for filing, including route, callsign, flight type, flight rules and equipment codes. Leave plan_id empty to get the latest dispatch. |
| get_aircraft_infoB | Aircraft details: ICAO/IATA type codes, registration, engines, equipment codes and passenger capacity. Leave plan_id empty to get the latest dispatch. |
| get_navlogA | Full navigation log with all waypoints: identifier, type, altitude, leg distance, leg time and fuel burn per leg. Use max_fixes to limit the number of fixes shown (default 50). Leave plan_id empty to get the latest dispatch. |
| get_notamsA | All NOTAMs for the flight (departure, arrival and en-route). Leave plan_id empty to get the latest dispatch. |
| get_alternate_infoA | Alternate airport details: ICAO code, planned runway, elevation, weather and alternate navlog. Leave plan_id empty to get the latest dispatch. |
| get_performanceB | Takeoff and landing performance data (TLR): takeoff distance, climb performance and landing calculations, if available for this aircraft type. Leave plan_id empty to get the latest dispatch. |
| get_crewB | Crew assignment for the flight: captain, first officer, dispatcher, purser and flight attendants. Leave plan_id empty to get the latest dispatch. |
| get_impactsA | Performance sensitivity analysis: fuel and time impact of changing cruise altitude or cost index. Leave plan_id empty to get the latest dispatch. |
| get_full_flight_planA | Complete flight plan as raw JSON (all sections except navlog, notams and alternate navlog). Useful for deep analysis or accessing fields not covered by the other tools. Leave plan_id empty to get the latest dispatch. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Every tool has a clearly distinct purpose targeting specific flight planning data (e.g., aircraft info, fuel plan, weather, NOTAMs), with no overlap or ambiguity. The descriptions precisely differentiate each tool's scope, making misselection unlikely.
All tools follow a consistent verb_noun pattern (get_*), using snake_case uniformly. This predictable naming scheme enhances readability and agent usability without any deviations or mixed conventions.
With 14 tools, the server is well-scoped for flight planning, covering essential aspects like navigation, performance, weather, and fuel. Each tool earns its place, providing comprehensive coverage without being excessive or thin for the domain.
The toolset offers near-complete coverage for flight planning, including data retrieval for aircraft, routes, fuel, weather, and performance. A minor gap exists in write/update operations (e.g., creating or modifying plans), but agents can work effectively with the provided read-only surface.