Establish the current state
Use get_run for the active task and run phase. Discover cockpit readings with list_groups and list_readings, then observe with read_group, read_reading, or read_flight_deck_indications. Do not infer that an earlier command succeeded merely because the tool call returned. Numeric readings can include a trend, previous value, and observation window; these can be null until enough history exists.
Select the procedure
Use list_checklist_categories to discover section IDs, then read_checklist with a section filter. Search the procedure name with search_docs, then read the matching detailed procedure with read_docs. The manual directory lists procedures in flight order. Follow the checklist conditions and expand each item’s Checks and evidence for the required observations.
Act and verify
Discover the active cockpit_* tool schemas and use the advertised actions, units, and ranges. Apply one action, inspect its verification result, and read the relevant indications. A group read is not an atomic snapshot; consider timing when comparing values. If an operation is unsupported, report the missing function with report_issue when useful.
Acknowledge progress
Only mark a checkable item after checking its conditions. Preserve the execution, section, and item IDs returned by the checklist. Acknowledgement records the pilot’s claim of completion; it does not move controls or verify simulator state. Update the run phase when the flight moves into its next phase.
Continue observing
Reassess after every consequential action and when conditions change. Read the MCP tools guide for detailed tool usage and procedure sequence for completion rules.
Example: Sydney to Canberra
Read the Sydney–Canberra flight-planning example for the route, waypoint coordinates, FMC legs, scenario performance assumptions and unit conversions.Last modified on October 30, 2026
