microsoft / microsoft/mcp

[BUG] Command names are inconsistent

Open
#2,627 3 comments 0 reactions 1 assignee Claimed by @alzimmermsft View on GitHub
bug needs-team-attention server-Azure.Mcp tools-Core
Dominant language
C#
Stars
3.7k
Forks
624
Avg merge
2d 20h
Merged PRs (30d)
220

Description

### Describe the bug

In the default namespace mode command names are inconsistent across tools. This makes it difficult for the LM to guess command names based on an established pattern. E.g., `acr_registry_list` vs. `sql_db_get` vs. `appservice_webapp_get`.

### Expected behavior

1. Command names use consistent terminology (e.g. `get` vs. `list`).
2. Command names should not start with the tool name. E.g. we should have `webapp_get` instead of `appservice_webapp_get`).

### Actual behavior

The inconsistency makes it difficult for the LM to guess a command name even when it knows exactly what it wants to do. For the azure-appservice tool I've seen it try all of the following before `appservice_webapp_get`:

> webapp get, webapp list, webapp_get, webapp_list, webapp_show, show, get, app_list, app_show, plan_list, plan_get, appserviceplan get, appserviceplan_get, config_get, appservice_get, webapp_config_appsettings_get

It ends up burning a lot of tokens and time trying to hit on the right command rather than doing useful work.

### Reproduction Steps

Ask Copilot to "get App Service details for ".

### Environment

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.