No user-submitted related servers found.
Scored across 34 tools
Most tools target a distinct resource and action, and the descriptions generally clarify boundaries between similar getters like get_recipe, search_recipes, and get_past_recipes. The main ambiguity is between run_agent_chef and next_actions, which both return an ordered due-actions checklist, though their intended entry points are described.
The vast majority of tool names follow a clear verb_noun pattern: get_, update_, add_, remove_, set_, record_, propose_, etc. Minor deviations like next_actions and message_group break the pattern slightly but are still understandable and not chaotic.
34 tools is a heavy surface for an MCP server, exceeding the 25+ threshold where tools generally become hard for an agent to navigate. Several peripheral or meta tools like dismiss_setup_checklist, get_connected_agents, record_schedule, and the overlapping run_agent_chef/next_actions pair make the set feel larger than necessary.
The core weekly meal-planning lifecycle is well covered: preferances, members, ingredients, recipe import/search/update, propose/vote/lock-in, grocery assemble/record, feedback, and history. Gaps include no manual recipe creation or recipe deletion and no grocery-order history lookup, but those are minor relative to the primary workflow.