Repository navigation
[4.0] Tool Inventory Audit and Redundant Command Consolidation #3987
Description
Release Tracker: microsoft/mcp-pr#691 (Theme 3.1)
Initiative: #3105 (Product and Platform)
Priority: P1 (Committed for 4.0)
Objective
Audit the Azure MCP tool catalog (500+ tools in 3.0) and consolidate overlapping, single-use, or redundant commands into cohesive tools to reduce token overhead and improve agent selection accuracy.
Scope
- Audit all service toolsets to identify overlapping operations (such as separate
get,list, andshowcommands that can be unified via optional filter parameters). - Use production tool invocation telemetry (
microsoft/mcp-pr#729) to identify unused or low-value commands and validate consolidation candidates. - Evaluate delegating generic resource metadata lookups to Azure Resource Graph where dedicated service commands add no unique value.
- Define backward-compatible command aliases and deprecation notices to prevent breaking existing prompts and workflows during transition.
- Update
consolidated-tools.json,azmcp-commands.md, ande2eTestPrompts.mdto reflect all merged commands.
Dependencies and Related Issues
- ARM Tool Consolidation & Phased Retirement:
microsoft/mcp#3142 - Tool usage and adoption telemetry dashboard:
microsoft/mcp-pr#729 - Vally multi-model selection verification:
microsoft/mcp-pr#638
4.0 Exit Criteria
- Complete tool rationalization catalog documenting old-to-new command mappings and rationale for each merge.
- Consolidated commands implemented with backward-compatible alias routing or migration guidance.
- All command changes reflected in
consolidated-tools.json,azmcp-commands.md, ande2eTestPrompts.mdand verified in Vally (microsoft/mcp-pr#638).
Activity
github-actions commentedon Oct 19, 2026
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @microsoft/azure-mcp.
github-actions commentedon Oct 19, 2026
Triaged as enhancement / Feature because this is planned Azure MCP command-surface consolidation work rather than a support question or a report of broken existing behavior. I set Priority = High: it is explicitly committed for 4.0 and has broad impact on Azure MCP usability through tool-count/token overhead, command discoverability, and agent selection accuracy, but it is not an active outage, security incident, or data-loss event and current functionality still has partial workarounds.
Added
tools-Corebecause the scope is cross-cutting command/catalog architecture for Azure MCP rather than a single service toolset; the existingserver-Azure.Mcpandneeds-team-triagelabels still fit. Owner recommendation:@g2vinayas the primary individual tools-Core owner in.github/CODEOWNERSand a prior assignee on related consolidation work (#2413, #1528). Related to #3142, but not obviously a duplicate.