No user-submitted related servers found.
Scored across 2 tools
The two tools have clearly distinct purposes: find_closest_stop locates the nearest stop based on coordinates, while find_stops searches by name. There is no overlap in functionality, making it easy for an agent to choose the right tool for each scenario.
Both tools follow a consistent verb_noun naming pattern (find_closest_stop, find_stops) with the same verb 'find'. The naming is predictable and readable, showing no deviations in style or convention.
With only two tools, the server feels thin for a public transport domain. While the tools cover basic stop lookup, there are likely missing operations such as route planning, schedule retrieval, or real-time arrivals, which are common in transport systems. The count is too low for the apparent scope.
The tool surface is significantly incomplete for a transport server. It lacks core functionalities like getting routes, schedules, or vehicle positions, which are essential for comprehensive transport queries. Agents will face dead ends when trying to perform common tasks beyond stop lookup.