@squawk/mcp 0.3.0 → 0.4.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/tools/flightplan.js +1 -1
- package/package.json +1 -1
package/dist/tools/flightplan.js
CHANGED
|
@@ -25,7 +25,7 @@ export function registerFlightplanTools(server) {
|
|
|
25
25
|
});
|
|
26
26
|
server.registerTool('parse_flightplan_route', {
|
|
27
27
|
title: 'Parse a flight plan route string',
|
|
28
|
-
description: 'Parses a whitespace-separated flight plan route string (e.g. "KJFK DCT MERIT J60 MARTN DCT KLAX") into structured route elements. Each token is classified as an airport, SID, STAR, airway, direct (DCT), waypoint, lat/lon coordinate, speed/altitude group, or unresolved. Airway tokens are expanded into waypoint sequences between the entry and exit fixes
|
|
28
|
+
description: 'Parses a whitespace-separated flight plan route string (e.g. "KJFK DCT MERIT J60 MARTN DCT KLAX") into structured route elements. Each token is classified as an airport, SID, STAR, airway, direct (DCT), waypoint, lat/lon coordinate, speed/altitude group, or unresolved. Airway tokens are expanded into waypoint sequences between the entry and exit fixes. SID/STAR tokens are expanded into their first common route, and the dotted PROCCODE.TRANSITION form (e.g. "NUBLE4.JJIMY") additionally merges the named transition\'s waypoints into the expansion.',
|
|
29
29
|
inputSchema: {
|
|
30
30
|
routeString: z
|
|
31
31
|
.string()
|