mcp-livedatapro

getTransitSchedule

Real-time train, metro, and bus schedules, platform numbers, and live delays (GTFS). Use when querying ground public transport (train, metro, bus) connections, platform numbers, and real-time GTFS delays between two stations. Do not use for aviation flights (use getLiveFlights) or private ride-hailing/taxi fares (use getTaxiEstimate). Returns next 10 chronological departures with live delay offsets and EUR fare estimates.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "origin_station": "<origin_station>",
      "destination_station": "<destination_station>"
    },
    "name": "getTransitSchedule"
  }
}

Input Schema

Name	Required	Description	Default
`departure_time`	No	Desired departure time in ISO-8601 or HH:MM 24-hour format (defaults to 'now').	now
`origin_station`	Yes	Origin city or official transit station name/code (e.g., London St Pancras, Budapest Keleti).
`destination_station`	Yes	Destination city or official transit station name/code (e.g., Paris Gare du Nord, Wien Hbf).

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 24, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / departure_time / default
```
Added value: +"now"
```
- addedInput schema / properties / departure_time / examples
```
Added value: +[
+  "08:30"
+]
```
- addedInput schema / properties / destination_station / examples
```
Added value: +[
+  "Paris Gare du Nord"
+]
```
- addedInput schema / properties / destination_station / minLength
```
Added value: +2
```
- addedInput schema / properties / origin_station / examples
```
Added value: +[
+  "London St Pancras"
+]
```
- addedInput schema / properties / origin_station / minLength
```
Added value: +2
```

Changed3 schema fields changedOct 24, 2026

changedInput schema / properties / departure_time / description

Previous value: -"ISO timestamp or HH:MM format"New value: +"Desired departure time in ISO-8601 or HH:MM 24-hour format (defaults to 'now')."

changedInput schema / properties / destination_station / description

Previous value: -"Destination city or station name/code"New value: +"Destination city or official transit station name/code (e.g., Paris Gare du Nord, Wien Hbf)."

changedInput schema / properties / origin_station / description

Previous value: -"Origin city or station name/code (e.g., London St Pancras, Budapest Keleti)"New value: +"Origin city or official transit station name/code (e.g., London St Pancras, Budapest Keleti)."

First observedOct 21, 2026

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full disclosure burden. It states the return shape ('next 10 chronological departures with live delay offsets and EUR fare estimates') and that data is real-time GTFS, but it omits auth requirements, rate limits, and how ambiguous station names are handled. Core behavior is clear, with modest gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is front-loaded: capability, then usage exclusions, then return format. There is minor repetition ('platform numbers' and 'real-time delays' recur in the first two sentences), but no sentence is wholly redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description must explain return values and does so concisely (10 departures, delay offsets, EUR fares). It also names alternatives. It is nearly complete for a 3-parameter tool, though it says nothing about empty results or whether multi-leg journeys are supported.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and each parameter (origin_station, destination_station, departure_time) is documented with examples and formats in the schema. The description adds only the framing 'between two stations'; it does not enrich parameter meaning beyond what the schema already provides, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource and verb: 'Real-time train, metro, and bus schedules, platform numbers, and live delays (GTFS).' It also explicitly distinguishes itself from siblings by naming getLiveFlights and getTaxiEstimate as alternatives, so an agent can route correctly without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use ('Use when querying ground public transport ... between two stations') and when-not-to-use with named alternatives ('Do not use for aviation flights (use getLiveFlights) or private ride-hailing/taxi fares (use getTaxiEstimate)'). No inference is required.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All mcp-livedatapro tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?