Related Servers

Many tools are near-duplicates of one another: `list_groups_ai_providers_prompts`, `list_admin_groups_by_group_ai_providers_prompts`, and `list_admin_groups_by_group_ai_providers_providers_by_prov` all appear to fetch AI prompts/providers, and the same pattern repeats for categories, tags, tools, foods, and households across admin/group/explore scopes. Descriptions are almost uniformly generic ('Get One', 'Get All', 'Create One'), so an agent gets no help in choosing between the household, group, and admin variants. Several names are truncated mid-word ('_by_prov', '_by_recip', 'categories_b'), making the intended target impossible to infer from the name alone.

There is a recognizable verb prefix convention (list_/get_/create_/update_/delete_/patch_), which saves this from being chaotic. However, names are literal renderings of URL paths, producing 60+ character identifiers that are truncated at arbitrary points, and at least one tool (`create_households_shopping_lists_by_item_recipe_by_rec_2`) has a numeric disambiguation suffix, which is a naming failure. Nearly duplicate names differing only in scope prefix make length-based confusion likely.

283 tools is an extreme mismatch for what is essentially one recipe-management application; it is a wholesale 1:1 mirror of the Mealie OpenAPI spec. Dozens of tools exist only because admin, group, and explore path variants were each generated separately. An agent cannot practically select from a surface this size without heavy filtering.

As a full API mirror, the surface covers essentially every lifecycle operation in the domain: recipe CRUD, bulk actions, imports/scraping, organizers, meal plans, shopping lists, households, users, auth, backups, and media. The redundancy across scopes actually guarantees no capability is missing, though it is far more than complete rather than efficiently complete.