Related Servers

With 188 tools, many have unclear or overlapping boundaries: calendar listing alone has list-calendar-events, list-specific-calendar-events, get-calendar-view, get-specific-calendar-view, list-calendar-view-delta, and list-calendar-events-delta. Download tools (download-bytes, download-bytes-to-file, get-download-url) and OneNote page creators (create-onenote-page vs create-onenote-section-page) are also easily confused, and list-excel-tables/get-excel-table share identical descriptions.

Most tools follow a readable kebab-case verb_noun pattern (list-, get-, create-, update-, delete-), but object terminology is inconsistent: drive vs onedrive (get-drive-item vs move-rename-onedrive-item), planner vs plan (get-planner-plan vs list-plan-buckets), and parallel actions diverge (create-draft-email vs create-reply-draft; add-excel-table-rows vs create-excel-table). The pattern is recognizable but not predictable enough for a 188-tool surface.

188 tools is an extreme count, far exceeding the 50+ threshold for a 1. Even for a broad Microsoft Graph wrapper, this is unwieldy and would be better split into purpose-specific servers for mail, calendar, files, Excel, OneNote, Planner, and To Do.

Despite the massive surface, the server has significant gaps: list-users, list-online-meetings, and get-schedule are all referenced in tool tips but are not actual tools, creating dead ends. Within covered domains, CRUD is incomplete (no delete-planner-task, no delete-onenote-section, no create/update/delete planner plan, no Outlook category update/delete), and major M365 areas like Teams, SharePoint sites, and admin are essentially absent.