Repository navigation
[Azure Advisor][Namespace] Failed to route correct mcp tool in namespace mode #3775
Description
Description:
Using prompts related to Azure Advisor:
- Find the Advisor service-retirement metadata with tracking ID QNY1-HB8
Agent rather use advisor_recommendation_list instead of expected tool advisor_metadata_list.
Steps to Reproduce:
- Start mcp server in
Namespacemode. - Open GitHub Copilot in VS Code.
- Enter the test prompt.
Environment:
- OS: Windows.
- Vscode Version: 1.138
- Large Language Model: GPT-5.6 Sol
- Azure MCP Server: 3.0.45
Expected Behavior:
The mcp tool could be routed correctly in namespace mode.
Rick Winter (@RickWinter) and Vinay Gera (@g2vinay) for notification
Activity
github-actions commentedon Sep 24, 2026
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @microsoft/azure-mcp.
github-actions commentedon Sep 24, 2026
Triaged as bug because this reports broken existing behavior: in namespace mode, the Advisor prompt routes to
advisor_recommendation_listinstead of the expectedadvisor_metadata_list.Added customer-reported because the failure was reported by an external user, and tools-ToolSelection because the core issue is incorrect tool selection/routing for the prompt. Existing area labels already point to Azure MCP Server and Advisor.
Set Priority to Medium: the issue is reproducible and impacts prompt reliability, but it appears limited to a specific routing scenario rather than a repo-wide blocker. Set Issue Type to Bug.
Owner recommendation: left blank for now. The issue clearly touches Advisor plus tool-selection behavior, but I do not have enough ownership context to confidently recommend a single primary owner from this workflow alone.