← Metro MCPCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Metro MCP
Snapshot Sep 30, 2026 · 23:10 UTC · version 6.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "metro-transit",
"description": "Use Metro MCP for live DC Metro or NYC Subway arrivals, stations, service incidents, accessibility, buses, trains, routes, and transfers.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 166
}
],
"skill_md_contents": "---\nname: metro-transit\ndescription: Use Metro MCP for live DC Metro or NYC Subway arrivals, stations, service incidents, accessibility, buses, trains, routes, and transfers.\n---\n\n# Metro Transit\n\nUse Metro MCP when a request depends on current public transit data in\nWashington, DC or New York City.\n\n## Choose the request\n\n- Identify `dc` or `nyc` from the user's location. Ask which city only when the\n request is genuinely ambiguous; do not silently choose one.\n- Search for a station before requesting predictions when the station name is\n partial or ambiguous. Preserve the user's selected station from any returned\n candidate list.\n- Use station predictions for arrivals, incidents for service disruptions, and\n elevator incidents for accessibility questions. Combine them when trip\n reliability depends on more than one feed.\n- Use bus stops or routes to resolve identifiers before requesting bus\n predictions or positions. Use train positions only when vehicle locations,\n rather than arrival estimates, answer the question.\n- Route information is richest for NYC. Do not imply unsupported DC route\n metadata exists.\n\n## Present results\n\n- Treat arrivals, incidents, outages, and vehicle positions as time-sensitive\n snapshots. State relevant update times when the tool returns them.\n- Name the city, station or route, direction, and units needed to interpret the\n result. Distinguish scheduled or estimated values from guarantees.\n- If the live feed is unavailable or has no result, say so plainly. Do not\n invent arrivals, incidents, accessibility status, fares, or service advice.\n- Metro MCP is anonymous and read-only. Never claim to buy fares, change\n service, send background alerts, or track a rider's location.\n"
}SHA-256: 6124bb2dc1b986655ef5af3e126e675bd11011ce0acf9d038c717c0a9d5df45a