paxaver-mcp

Each tool targets a distinct resource-action pair (e.g., list_school_events vs list_my_event_registrations, create_lunch_order_draft vs pay_lunch_order_draft). Overlaps like archive_restaurant_menu_item vs update_restaurant_menu_item (is_active=false) are explicitly clarified in descriptions, so an agent can reliably choose the right tool.

All tool names use consistent snake_case verb_noun patterns, with clear prefixes like list_, create_, update_, cancel_, get_, and a 'my_' modifier for user-scoped operations. The structure is predictable throughout, making names easy to parse and remember.

26 tools is on the heavy side (borderline per rubric), but the set spans several distinct subdomains—restaurants, menu scheduling, lunch orders, events, volunteer signups, wallet, and context—each requiring its own operations. No tools appear redundant, though some grouping could reduce the count.

Core workflows are well covered: full CRUD for menu items and events, draft-to-pay lunch order lifecycle, and event/volunteer registration management. A notable gap is the lack of update/delete for school restaurants (explicitly delegated to the admin panel), and no explicit shift management tools beyond signup, but agents can work around these.