Skip to content

Conversation

vcolin7
Copy link
Contributor

@vcolin7 vcolin7 commented Sep 18, 2025

What does this PR do?

This pull request adds a new --namespaces option to the azmcp tools list command, allowing users to list top-level service namespaces instead of individual commands. It also introduces a count field in the output to indicate the number of top-level namespaces and their subcommands. Tests and documentation have been updated accordingly.

GitHub issue number?

N/A

Pre-merge Checklist

  • Required for All PRs
    • Read contribution guidelines
    • PR title clearly describes the change
    • Commit history is clean with descriptive messages (cleanup guide)
    • Added comprehensive tests for new/modified functionality
    • Updated servers/Azure.Mcp.Server/CHANGELOG.md and/or servers/Fabric.Mcp.Server/CHANGELOG.md for product changes (features, bug fixes, UI/UX, updated dependencies)
  • For MCP tool changes:
    • One tool per PR: This PR adds or modifies only one MCP tool for faster review cycles
    • Updated servers/Azure.Mcp.Server/README.md and/or servers/Fabric.Mcp.Server/README.md documentation
    • Updated command list in /docs/azmcp-commands.md and/or /docs/fabric-commands.md
    • For new or modified tool descriptions, ran ToolDescriptionEvaluator and obtained a score of 0.4 or more and a top 3 ranking for all related test prompts
  • Extra steps for Azure MCP Server tool changes:
    • Updated test prompts in /docs/e2eTestPrompts.md
    • 👉 For Community (non-Microsoft team member) PRs:
      • Security review: Reviewed code for security vulnerabilities, malicious code, or suspicious activities before running tests (crypto mining, spam, data exfiltration, etc.)
      • Manual tests run: added comment /azp run mcp - pullrequest - live to run Live Test Pipeline

@vcolin7 vcolin7 added this to the 2025-09 milestone Sep 18, 2025
@vcolin7 vcolin7 self-assigned this Sep 18, 2025
@vcolin7 vcolin7 requested review from a team as code owners September 18, 2025 18:19
@vcolin7 vcolin7 added the server-Azure.Mcp Azure.Mcp.Server label Sep 18, 2025
@vcolin7 vcolin7 added the Tool Selection Issues related to ensuring the right tool for the job is selected by an LLM/coding agent label Sep 18, 2025
@vcolin7 vcolin7 changed the title Tools list as namespaces Add --namespaces switch to azmcp tools list Sep 18, 2025
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds a new --namespaces option to the azmcp tools list command that returns top-level service namespaces with their subcommands instead of a flat list of all commands. It also introduces a count field to provide quantitative information about namespaces and commands.

  • Added --namespaces flag to list top-level service namespaces with their subcommands
  • Introduced SubcommandsCount field to CommandInfo and ResultsCount field to CommandResponse
  • Updated documentation and comprehensive test coverage for the new functionality

Reviewed Changes

Copilot reviewed 5 out of 7 changed files in this pull request and generated 2 comments.

Show a summary per file
File Description
ToolsListCommand.cs Implements the new --namespaces option logic and count field population
CommandInfo.cs Adds SubcommandsCount field to track number of subcommands
CommandResponse.cs Adds ResultsCount field to track total number of results
ToolsListCommandTests.cs Comprehensive test coverage for new namespace functionality and count fields
azmcp-commands.md Documentation updates for the new option and count fields

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
@joshfree joshfree moved this from Untriaged to In Progress in Azure MCP Server Sep 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
server-Azure.Mcp Azure.Mcp.Server Tool Selection Issues related to ensuring the right tool for the job is selected by an LLM/coding agent
Projects
Status: In Progress
Development

Successfully merging this pull request may close these issues.

4 participants