db-fahrplan-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DB_API_KEY | Yes | Your DB API key | |
| DB_CLIENT_ID | Yes | Your DB API Client ID |
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 |
|---|---|
| find_stationA | Search German train stations and get their EVA numbers. Args: pattern: Station name, EVA number, or DS100 code. Prefix search - exact DB naming works best (e.g. "Stolberg(Rheinl)Hbf" rather than "Stolberg Hbf"). Umlauts often fail; try "*" as wildcard. |
| get_departuresA | Get the timetable for a station within one hour slice, including real-time data: delays (delay_minutes), platform changes, cancellations, and added trips such as replacement buses. Defaults to the current date and hour. Args: eva_no: EVA number of the station (e.g. "8000001" for Aachen Hbf). Use find_station to look it up. date: Day in YYMMDD format (e.g. "260713"). Defaults to today. hour: Hour in HH format, 00-23. Defaults to the current hour. |
| get_live_changesA | Get all known real-time changes for a station: delays, platform changes, cancellations. Covers the current operating day. Args: eva_no: EVA number of the station (e.g. "8000001" for Aachen Hbf). limit: Maximum number of stops to return (sorted by time). |
| get_recent_changesA | Get only the changes of the last 2 minutes for a station. Much smaller than get_live_changes - use for frequent polling. Args: eva_no: EVA number of the station (e.g. "8000001" for Aachen Hbf). limit: Maximum number of stops to return (sorted by time). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Tools have distinct purposes, but get_live_changes and get_departures both include real-time data like delays and platform changes, which could cause minor confusion. However, descriptions clarify the difference in scope (whole day vs. one hour slice).
All tools follow a consistent verb_noun pattern with lowercase and snake_case (e.g., find_station, get_live_changes). The verbs are descriptive and uniform (find, get).
With 4 tools, the server is well-scoped for its purpose of station lookup and real-time departure/changes monitoring. Each tool provides necessary functionality without redundancy.
The set covers station search, departures per hour, full-day changes, and recent changes. Missing are features like train journey details or historical data, but for station-focused real-time information, it's nearly complete.