Distribute centralized files like consolidated-tools.json into tools/ directories
- Dominant language
- C#
- Stars
- 3.7k
- Forks
- 624
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 220
Description
As part of the original Areas migration (https://github.com/Azure/azure-mcp/pull/426), a lot of work was done to remove any files that had to be updated every time a tool was added.
It seems we've regressed back to central tool files:
[consolidated-tools.json](https://github.com/colbytimm/microsoft-mcp/blob/main/core/Azure.Mcp.Core/src/Areas/Server/Resources/consolidated-tools.json)
[prompts.json](https://github.com/colbytimm/microsoft-mcp/blob/main/eng/tools/ToolDescriptionEvaluator/prompts/prompts.json)
[namespace-tools.json](https://github.com/colbytimm/microsoft-mcp/blob/main/eng/tools/ToolDescriptionEvaluator/prompts/namespace-tools.json)
[consolidated-prompts.json](https://github.com/colbytimm/microsoft-mcp/blob/main/eng/tools/ToolDescriptionEvaluator/prompts/consolidated-prompts.json)
It looks like the data in these files could be divided into the tools/ directories instead of being centralized.
If not distributed, the files in the eng/ directory should be moved to the Azure server or core directory as they don't apply to all servers in the repo.
Contributor guide
Research direction
Start by reviewing the original Areas migration in Azure/azure-mcp PR 426, then inspect consolidated-tools.json and the three files under eng/tools/ToolDescriptionEvaluator/prompts. Determine how their data maps to the tools/ directories and whether the eng files belong under the Azure server or core directory. Done means tool data is no longer maintained in centralized files, or the files are relocated to the appropriate server or core area.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100