flight-tracker · git:20260813.48597a3 · 2026-08-13 · sha256 c8c73a4d6a610ff6
flight-tracker git:20260813.48597a3A
Immutable. This exact content is served forever at /api/v1/blob/c8c73a4d6a610ff6.
--- name: flight-tracker description: "Track flight status, delays, gate changes, and estimated arrival times for any commercial flight. Covers real-time flight tracking, schedule lookup, and delay monitoring for travel coordination and logistics planning." --- # Flight Tracker Track flight status, delays, gate changes, and estimated arrival times for any commercial flight. Covers real-time flight tracking, schedule lookup, and delay monitoring for travel coordination and logistics planning. Read [the API map](references/sandbase-api-map.md) before selecting a capability. ## Call SandBase capabilities For every selected tool, call `sandbase_describe_tool` first and use only arguments in its current input schema. Then call `sandbase_call_tool` with the exact `tool_name`. ## Available Tools - `strale_flight_status` ## Workflow 1. Understand the user's research question, target, and context. 2. Call `sandbase_describe_tool` for each selected tool to confirm parameter schema. 3. Call `sandbase_call_tool` with the exact tool_name and schema-defined arguments. 4. Synthesize findings into a clear, evidence-backed answer. 5. Cite sources, note evidence gaps, and separate observations from interpretations. ## Guidelines - Always call `sandbase_describe_tool` before using any capability. - Cite sources and preserve attribution (URLs, usernames, dates, metrics). - Separate factual observations from analysis and recommendations. - If data is unavailable, note the gap and continue with available evidence. - Read-only research only. Never take actions on platforms.