Skip to content

[Namespace mode] Querying VM availability status routed to wrong tool (expected resourcehealth_availability-status_get) #1999

@Menghua1

Description

@Menghua1

Description:
In Namespace mode, entering the prompt What is the availability status of virtual machine <vm_name> in resource group <resource_group_name>? should trigger resourcehealth_availability-status_get, but instead compute_compute_vm_get is triggered, as follows:
Image

Steps to Reproduce:

  1. Start mcp server in Namespace mode.
  2. Open GitHub Copilot in VS Code and switch to Agent mode.
  3. Click Refresh on the tools list, and select the MCP Server: Azure MCP.
  4. Enter the test prompt What is the availability status of virtual machine <vm_name> in resource group <resource_group_name>?.

Environment:

  • OS: Windows.
  • Vscode Version: 1.109.5
  • GitHub Copilot Chat Version: 0.37.9
  • Large Language Model: Claude Sonnet 4.5
  • Azure MCP Server: 2.0.25

Expected Behavior:
The prompt What is the availability status of virtual machine <vm_name> in resource group <resource_group_name>? can successfully trigger the expected mcp tool.

@joshfree and @g2vinay for notification

Metadata

Metadata

Assignees

Type

No type

Projects

Status

Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions