Czech Railways (České dráhy) MCP Server
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_locationsA | Search for train stations and cities in the Czech Railways network. Use this to find station codes for connection searches. |
| search_connectionsB | Search for train connections between two stations. Returns available trains with departure times, duration, and transfers. |
| get_connection_detailsA | Get detailed information about a specific train connection. Note: This endpoint is not available with the mobile API - all connection details are included in search results. |
| get_passenger_typesA | Get a list of available passenger types and discount categories (e.g., adult, child, senior, student discounts). |
| get_price_offerB | Get a price offer for a specific connection. Note: Prices are already included in connection search results, so this separate endpoint is not available with the mobile API. |
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 5 tools
Tools have distinct purposes, but get_connection_details and get_price_offer are noted as redundant with search results, which could cause agent confusion if they attempt to use them and fail.
All tool names follow a consistent verb_noun pattern using snake_case: get_* and search_*. No naming anomalies.
5 tools is a reasonable size for a railway information server, but two tools are marked as unavailable with the mobile API, suggesting they could be removed.
Covers basic query operations (search stations, connections, passenger types), but lacks booking, real-time info, or station details, and duplicate tools reduce practical completeness.