No user-submitted related servers found.
Scored across 15 tools
Most tools clearly target distinct resources and actions, such as MXD inspection, dataset metadata, feature queries, and exports. The main ambiguity is between run_geoprocessing and run_advanced_geoprocessing, and the multiple export_mxd_* variants require careful reading to avoid misselection.
Names generally follow a readable verb_noun snake_case pattern, e.g., list_mxd_layers, describe_dataset, export_mxd_to_png. Minor inconsistencies like health_check and the awkward export_mxd_with_overlay_png keep it from being perfectly uniform.
Fifteen tools is at the upper bound but each one earns its place across the ArcMap server's broad scope: health checks, capability discovery, dataset/MXD inspection, feature queries, exports, and geoprocessing. There is no obvious redundancy or bloat.
The core read, query, export, and geoprocessing workflows are well covered, especially with scratch-confirmed write paths. Minor gaps exist, such as no workspace-content listing or general MXD editing beyond layer visibility, but these do not break the main workflows.