No user-submitted related servers found.
Scored across 28 tools
Most tools target a distinct resource+action (devices, users, tags, config profiles, apps, enrollments, DEP), and descriptions explicitly cross-reference each other (e.g. list_custom_attributes -> set_device_custom_attribute). A few boundaries blur: list_suspended_devices is largely a filtered list_devices, device_health_summary overlaps with list_devices filters, get_device_locations duplicates a get_device detail area, and query_miradore is a catch-all that could tempt an agent away from the specific read tools. These are minor and the descriptions steer correctly.
The dominant pattern is consistent snake_case verb_noun (list_devices, get_device, add_device_tag, deploy_application, update_user), which is easy to predict. Deviations are minor but present: device_health_summary is noun-first with no verb, query_miradore uses a domain suffix rather than a resource noun, and tag verbs are inconsistently pluralized (add_user_tags vs remove_user_tag).
At 28 tools the surface sits above the comfortable band, though the domain is genuinely broad (devices, users, tags, config profiles, applications, enrollments, DEP sync) and no two tools are redundant. The count is defensible but heavy: several list_* reads could be consolidated as filters on a single listing tool.
Core MDM workflows are covered, but the lifecycle is asymmetric: activate_device exists to un-retire devices while no retire_device is offered, deploy_application and deploy_config_profile have removal counterparts only for profiles (no app removal), tags can be listed and attached but never created or deleted, and there is no list_applications (get_application requires an ID from the console URL). Users can be created and updated but not deleted or deleted-from-device.