F
licenseB
qualityC
maintenanceProvides auditable Mumbai route lateness metrics, including route ranking, performance summaries, and trip-level evidence, derived from a reloadable CSV dataset.
3
-
Cityflo OTP MCP
by Sonu0305
Related Servers
Alternatives to Cityflo OTP MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceAnswers operational questions about route on-time performance, such as lateness rates and trip evidence, using structured tools for route summary, trip lateness, and data quality.-
- FlicenseNot gradedqualityCmaintenanceA dependency-free MCP server for Mumbai North operations that computes route lateness metrics, exposes underlying late trips, and reports data quality issues to answer whether a route was late and by how much.-
- FlicenseNot gradedqualityCmaintenanceAnswers whether a route ran late and by how much, with drill-down into individual trip delays and an audit trail of data-quality exclusions and duplicate resolutions.-
- FlicenseNot gradedqualityDmaintenanceCompute and analyze bus route lateness using trip data, with drill-down and cross-referencing against rider complaints and operational logs.-
- FlicenseNot gradedqualityCmaintenanceMCP server for analyzing bus route on-time performance, providing lateness summaries, trip drill-downs, and flagged data reports.-
TDQS
A3.7/5.0
Scored across 3 tools
Disambiguation5/5
Each tool targets a distinct level of analysis: route-level aggregate OTP, trip-level late-trip detail, and data-quality context for quarantined rows. The descriptions explicitly frame list_late_trips as a drill-down from route_otp_summary, so there is no real overlap.
Naming Consistency4/5
All names use lowercase snake_case and clearly describe their output, but they do not follow a single verb_noun pattern: two are noun phrases (route_otp_summary, data_quality_report) and one uses a verb (list_late_trips). This is a minor stylistic deviation rather than a major inconsistency.
Tool Count5/5
With three tools, the server is tightly scoped to OTP reporting: summary, drill-down, and data quality. Each tool has a clear purpose and none feel redundant.
Completeness4/5
The tools cover the core read-only OTP workflow: aggregate summary, late-trip detail, and explanation of excluded data. A route enumeration tool would be a useful addition, but agents can work around this when route IDs are supplied.
Maintenance
ActivitySlowing
ResponsivenessNo issues