db-fahrplan
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| db_search_stationA | Find Deutsche Bahn stations by name. Call this only when a name is ambiguous or another
tool rejected it; the other tools accept plain station names directly. Returns name, EVA
number ( |
| db_journeysA | Plan train connections between two stations with live bahn.de data. Each connection: dep/arr (real-time; '(+7)' = 7 min late, '(+1d)' = next day), duration,
changes, price in EUR for the given travellers/BahnCard (None with Deutschlandticket), load
(occupancy) per class, |
| db_journey_offersA | All fares bahn.de offers for ONE specific connection (Super Sparpreis, Sparpreis, Flexpreis, regional day tickets…) with price and class, re-checked live. Use after db_journeys when the user asks 'how much' or 'cheapest ticket'. Prices are informational, not a booking. |
| db_best_priceA | Bestpreissuche: the cheapest available fare in each time band of a day (00–07, 07–10, 10–13, 13–16, 16–19, 19–24) with the connection it applies to. Use for 'when is it cheapest to go'. Typically only meaningful for long-distance routes booked in advance. |
| db_departuresA | Live departure board: time (real-time, with delay), line, destination, platform (real-time,
|
| db_arrivalsC | Live arrival board, same shape as db_departures (direction = origin). |
| db_trip_detailsA | Every stop of one specific train run with scheduled and real-time arrival/departure, platform (real-time), load, and notes — i.e. 'where is this train now, is my stop still served, which platform at my stop'. Also returns train amenities and running days. |
| db_nearbyA | Stations and stops around a GPS position — 'stations near me'. Returns name, EVA number,
products, and the bahn.de |
| db_train_formationA | Coach order and platform sectors for a long-distance train at a station: which sector (A–G) 1st class, bistro, bike and quiet coaches stop at, and the real-time platform. Answers 'where do I stand on the platform'. ICE/IC/EC only; not available for regional trains. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| plan_trip | Guided trip planning: connections, then fares, then platform advice. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct task: station search, journey planning, fare offers, best-price search, departures, arrivals, trip details, nearby stations, and train formation. The only mild overlap is between db_journey_offers and db_best_price (both fare-related), but their specific purposes and usage cues keep them distinguishable.
All tools consistently use the `db_` prefix and clear domain vocabulary. Minor inconsistency: `db_search_station` is verb-based while most others are noun phrases (`db_journeys`, `db_departures`), but the overall pattern is still predictable and readable.
Nine tools is well-scoped for a rail travel information server. Each tool covers a distinct user need without unnecessary duplication or overwhelming breadth.
The tool set covers the full journey information workflow: station discovery by name or GPS, journey planning, fare comparison, live departures/arrivals, per-trip stop details, and train formation. There are no obvious dead ends or significant missing operations for the stated domain.