OpenDataMCP
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
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rail-traffic-infoC | Fetch rail traffic information |
| railway-linesC | Fetch railway line information |
| rolling-stockC | Fetch rolling stock (vehicle) information |
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 3 tools
Each tool targets a reasonably distinct resource: traffic information, railway lines, and rolling stock. However, rail-traffic-info and railway-lines could be confused in situations involving line status or operations, since both could plausibly return similar operational information.
All tool names use lowercase hyphenated noun phrases, which gives the set a consistent overall style. The minor inconsistency between 'rail', 'railway', and 'rolling-stock' is noticeable but does not cause significant confusion.
Three tools is on the lean side, but each one covers a meaningful area of rail open data: traffic, infrastructure, and vehicles. The count is reasonable for a specialized read-only data server, though it could be expanded.
The set covers several core rail datasets, but there are obvious gaps such as stations, schedules, departures, and disruptions unless they are implicitly included in traffic info. Agents working with broader rail queries would likely need additional tools.