Skip to content

[4.0] Prototype and Benchmark Higher-Level Grouped Discovery Mode #3988

Description

Release Tracker: microsoft/mcp-pr#691 (Theme 1.4)
Initiative: #3105 (Product and Platform)
Priority: P1 (Decision Needed for 4.0 Default Mode)

Objective

Prototype and benchmark a higher-level grouped discovery mode (group -> service/namespace -> command) as a candidate for the default server mode in 4.0, balancing initial tool-list footprint against discovery hop overhead.

Scope

  • Introduce a high-level grouping layer above service namespaces, establishing a group -> service/namespace -> command discovery path (adding one discovery hop compared with namespace mode).
  • Benchmark the grouped mode prototype against namespace mode and consolidated mode (microsoft/mcp#849) using identical models, clients, and representative single-service and cross-service workflows.
  • Measure end-to-end metrics across the evaluation matrix:
    • Total end-to-end token consumption (including discovery turns)
    • Tool-selection and parameter-binding accuracy
    • Task-completion success rate
    • End-to-end latency, accounting for additional discovery round trips
  • Keep grouped mode opt-in during evaluation while preserving namespace mode as the fallback until empirical results justify any default-mode change.

Dependencies and Related Issues

  • Experiment-Driven Tool Evaluation Epic: microsoft/mcp#3035
  • Consolidated Mode comparison counterpart: microsoft/mcp#849
  • Vally selection accuracy harness: microsoft/mcp-pr#638
  • Latency and token budget benchmark harness: microsoft/mcp-pr#637

4.0 Exit Criteria

  • Grouped mode prototype implemented behind an opt-in --mode configuration.
  • Comparative benchmark report completed for Grouped Mode vs. Namespace Mode vs. Consolidated Mode across single-service and cross-service workflows.
  • Default startup mode decision recorded for 4.0 GA with namespace mode retained as a supported fallback.

Activity

  1. added
    needs-team-attentionWorkflow: This issue needs attention from Azure service team or MCP team.
    tools-CoreAZMCP Core functionality that all other tools build on top of
    on Oct 19, 2026
  2. github-actions commented on Oct 19, 2026

    @github-actions
    Contributor

    Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc Alan Zimmer (@alzimmermsft) Vinay Gera (@g2vinay) @microsoft/azure-mcp.

  3. github-actions commented on Oct 19, 2026

    @github-actions
    Contributor

    Triaged as enhancement / Feature because this tracks a new Azure MCP server capability and a 4.0 default-mode decision rather than a broken existing behavior.

    Priority: High — this work influences the Azure MCP 4.0 startup-mode decision for a core discovery path and needs benchmark data before GA, but it is not an active service outage.

    Labels: no new labels added. The existing enhancement, server-Azure.Mcp, tools-Core, and needs-team-attention labels already match the issue scope.

    Owner recommendation: keep @alzimmermsft as the primary owner; the current assignment aligns with the existing tools-Core routing in CODEOWNERS.

    Generated by Issue Triage Agent for #3988 · copilot · gpt54 · 15.6 AIC · ⌖ 4.7 AIC · ⊞ 32.9K · ◷

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestneeds-team-attentionWorkflow: This issue needs attention from Azure service team or MCP team.server-Azure.McpAzure.Mcp.Servertools-CoreAZMCP Core functionality that all other tools build on top of

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions