tods-mcp
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tods_inspect_feedA | Inspects a TODS (Transit Operational Data Standard) directory or .zip feed. Returns high-level statistics, table list, supplement counts, crew runs, and fleet totals. |
| tods_merge_supplementsC | Applies the official TODS v2.1.0 supplement merge algorithm (_supplement.txt files onto base GTFS files). Returns merge summary, additions, deletions, updates, and diffs. |
| tods_validate_feedB | Runs comprehensive TODS v2.1.0 validation against the dataset: primary key uniqueness, foreign key consistency (run_events -> supplemented calendar/trips/stops), non-overlapping trip runs, time format/chronology, and TODS_delete rules. |
| tods_get_runsA | Queries operational crew runs from run_events.txt. Returns chronological duty events, report/clear times, pieces of work, and total duty duration. |
| tods_get_vehicle_assignmentsC | Queries fleet vehicle assignments to blocks and dates from vehicle_assignments.txt and vehicles.txt. |
| tods_get_deadheadsC | Extracts deadheads, yard pulls, non-revenue positioning trips, and depot movements identified in trips_supplement.txt or run_events.txt. |
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 6 tools
Each tool targets a distinct operation: inspection, merging, validation, and entity-specific queries for runs, vehicle assignments, and deadheads. There is no meaningful overlap because inspect/validate/merge have clearly different outputs and each get_ tool is scoped to a different TODS entity.
All tools consistently use the tods_ prefix followed by a verb_noun pattern: inspect_feed, merge_supplements, validate_feed, get_runs, get_vehicle_assignments, get_deadheads. No mixed casing, inconsistent verbs, or irregular naming conventions are present.
Six tools is a well-scoped count for a TODS-specific server. The set covers feed-level operations and targeted queries without redundancy or unnecessary bloat.
The surface covers the main TODS workflows: inspect, merge supplements, validate, and query core operational entities. Minor conveniences like a dedicated vehicle-only query or raw table access are missing, but these are workaroundable and do not create dead ends.