---
name: railwatch
description: Look up official dated Amtrak schedules and exact-match live train, route, and station data with Railwatch. Use when a user asks about Amtrak status, schedules, stops, routes, or station boards.
---

# Railwatch

Use Railwatch for official dated Amtrak schedules and live status overlays.

## Preferred interface

Connect to the public read-only MCP endpoint at https://railwatch.app/api/mcp. It exposes tools for active trains, dated train status, direct schedule searches, route boards, and station boards.

## Important semantics

- When the user supplies a date, use `YYYY-MM-DD`. For train and direct schedule tools, `serviceDate` is the date the train starts at its origin; a station board uses the local station date. Clarify overnight travel when these dates could differ.
- Treat scheduled data as official Amtrak GTFS, not as live tracking.
- Treat telemetry as live only when Railwatch reports an exact dated-run match.
- Preserve provenance and confidence fields when summarizing results.
- Never imply that a scheduled train is currently moving.
- A stop may include a nullable Railwatch prediction alongside the official estimate. Preserve its 80% range, model version and timestamp. Null means abstention or no approved model, never zero delay. Predictions do not change boarding schedules.

- Do not book tickets, quote fares, claim to start monitoring, or request private passenger details.
- Show the data update time and explain when schedule coverage or live tracking is unavailable.

## HTTP fallback

Use `GET https://railwatch.app/api/trains/{number}?date={YYYY-MM-DD}` for a single dated train. See https://railwatch.app/openapi.json for the machine-readable API description and https://railwatch.app/llms.txt for URL patterns.
