Model Context Protocol (MCP) Server for Madurai CityBus transit routing, official stage fares, stop search, and platform bay departures.
Four well-named tools with complete input schemas and solid descriptions (avg 180 chars). All parameters are typed and described. Tool names follow verb_noun convention (search_*, get_*, calculate_*). Schemas use proper JSON Schema with required fields and defaults. However, output schemas are not formally documented in the code, responses are constructed as markdown text rather than structured objects. Error handling is basic (generic error wrapping). No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite all tools being read-only. Parameter descriptions include helpful examples and constraints (e.g., 'verbose=true for complete stop sequences'). Missing: per-tool output schema documentation, structured response objects, and error recovery guidance.
Calculate the official TNSTC stage fare between any boarding and alighting bus stop in Madurai across Ordinary, LSS, Express, and Deluxe/AC classes based on authoritative stage charts.
Lookup route details, platform bay at Periyar Bus Stand, spoke category, and stop sequence for a specific Madurai bus number (e.g. '44', '77', '11A', '5'). By default returns key transit milestones for token efficiency; set verbose=true for the complete numbered stop list.
Search bus routes between two stops in Madurai. Returns direct buses and 1-transfer options with stop counts, PBS platform bays, official TNSTC stage fares, and canonical visual map links. By default returns key milestones for token efficiency; set verbose=true for complete stop sequences.
Bilingual (English and Tamil) autocomplete and search for bus stops across Madurai. Returns canonical name, Tamil script name, spoke corridor, route frequency, and verified GPS coordinates if available.
Output schemas not formally documented. Responses are constructed as markdown text blocks rather than structured JSON objects with typed fields. LLMs cannot reliably extract data for downstream tool chaining.
No tool annotations despite all tools being read-only. Missing readOnlyHint declarations that would signal to agents these are safe, non-destructive operations.
Error handling is generic. Errors return plain text messages without categorization (retryable vs user-fixable vs fatal) or recovery guidance. Example: 'No bus routes found' lacks suggestion to try major hubs.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 65 | 2026-07-28+ | v2 |
calculate_fare has optional bus_number parameter but no documentation of how it affects fare calculation or when to use it. Dependency between parameters is undocumented.
search_bus_stops accepts 'query' as free-form string with no constraints. No enum, pattern, or length limits documented. LLMs may pass invalid or excessively long queries.