lametro_service_cancellations
Pack: la-metro · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)
No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/lametro_service_cancellations for the schema, then POST the same URL with its arguments for the data.
Trips LA Metro has canceled on the current service day, counted per route. This is LIVE operational data and the one real-time signal LACMTA publishes publicly — AUTHORITATIVE for “is LA Metro dropping trips on my line today”, which no schedule or GTFS feed can answer. Sorted worst-affected first.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
route_code | string | no | Optional: report only this route code (e.g. “251”). Omit for every affected route. |
min_canceled | number | no | Optional: only report routes with at least this many canceled trips. |
Example call
Arguments
{
"min_canceled": 5
}
curl
curl -X POST https://gateway.pipeworx.io/la-metro/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"lametro_service_cancellations","arguments":{"min_canceled":5}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('lametro_service_cancellations', {
"min_canceled": 5
});
More examples
{
"route_code": "720"
}
Connect
Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:
{
"mcpServers": {
"pipeworx": {
"url": "https://pipeworx.io/mcp"
}
}
}
Connect to just the la-metro pack
{
"mcpServers": {
"la-metro": {
"url": "https://gateway.pipeworx.io/la-metro/mcp"
}
}
}
See Getting Started for client-specific install steps.