No user-submitted related servers found.
Scored across 84 tools
The set covers many distinct Dynamics 365 subdomains, but several tools overlap in purpose, especially metadata readers (get_model_definition, get_entity_metadata_summary, get_detailed_field_metadata, list_all_entity_definitions), choice readers (get_field_picklist_options, get_model_choices), and relationship readers (get_model_relationship, get_entity_navigation_links). The very detailed descriptions help disambiguate most cases, but with 84 tools there is still meaningful selection risk.
Most names are snake_case verb_noun, but the d365_plugin_* family uses noun_verb forms such as d365_plugin_assembly_inspect and d365_plugin_steps_query, while other areas use create_model_*, get_model_*, and generic record verbs. The conventions are mixed but generally readable.
84 tools is far beyond the 50+ threshold for an extreme mismatch, even for a large enterprise platform like Dynamics 365. The surface should be consolidated or split into smaller purpose-specific servers to reduce cognitive load.
The server covers records, metadata, solutions, ribbon, plugins, web resources, audit, security, diagnostics, and querying, but lifecycle coverage is uneven. Notable gaps include no create_solution, no remove_solution_component, no delete_web_resource, no delete_plugin_step, and no delete operations for model tables, columns, relationships, or keys.