No user-submitted related servers found.
Scored across 8 tools
Three tools (list_locations, get_hours, find_open_now) all return halls with service periods, and their boundaries rely on subtle distinctions like openNow vs. time-of-day filtering vs. weekly schedule. get_menu vs filter_dishes and get_item_nutrition vs list_nutrition_fields are better separated thanks to explicit cross-references in the descriptions, but the hours/location cluster remains overlapping.
All eight tools follow a consistent snake_case verb_noun pattern (get_menu, list_locations, filter_dishes, find_open_now), with verb choice reflecting intent (get for single-resource, list for enumeration, filter/find for queries). No naming style mixing.
Eight tools is well-scoped for a dining-hall domain: menu retrieval, filtering, hours, locations, occupancy, and nutrition each get focused coverage without redundancy in count. No tool feels like filler.
The surface covers menus, filtering, nutrition fields/panels, hours, location status, and occupancy, with cafes/markets/prices explicitly declared out of scope. Minor gaps: no multi-hall raw menu retrieval (only filter_dishes sweep) and dish lookup is name-based only, but agents can work around these.