Tool list testcase

[anannya03]

What does this PR do?

Added Unit testcases for the ToolListCommand.cs file.

Command- azmcp tool list
Function: List all available tools in the Azure MCP server.

GitHub issue number?

[Link to the GitHub issue this PR addresses]

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 CHANGELOG.md for product changes (features, bug fixes, UI/UX, updated dependencies)
  • Spelling check passes: .\eng\common\spelling\Invoke-Cspell.ps1
• For MCP tool changes, updated:
  • Updated README.md documentation
  • Updated command list in /docs/azmcp-commands.md
  • Updated test prompts in /e2eTests/e2eTestPrompts.md
• 👉 For Community (non-Azure 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 azure - mcp to run Live Test Pipeline

[Copilot]

Pull Request Overview

This PR adds comprehensive unit tests for the ToolsListCommand.cs functionality, which implements the azmcp tool list command that lists all available tools in the Azure MCP server. The tests validate various scenarios including successful execution, error handling, JSON serialization, and command structure validation.

Key changes:

• Added 10 comprehensive test methods covering normal operation, error scenarios, and edge cases
• Implemented proper mocking and service provider setup for isolated testing
• Added validation for command structure, filtering, and metadata properties

Comments suppressed due to low confidence (2)

core/tests/AzureMcp.Core.UnitTests/Areas/Tools/UnitTests/ToolsListCommandTests.cs:147

• This test assertion appears to be checking that the 'list' command is filtered out, but the logic is unclear and may not be testing the intended behavior. The test name suggests it should verify hidden commands are filtered, but this assertion doesn't clearly demonstrate what constitutes a 'hidden' command.

        Assert.DoesNotContain(result, cmd => cmd.Name == "list" && cmd.Command.Contains("tool"));

core/tests/AzureMcp.Core.UnitTests/Areas/Tools/UnitTests/ToolsListCommandTests.cs:149

• This assertion is redundant as it only verifies that at least one command has a non-empty name, which is already covered by the earlier loop validation in ExecuteAsync_WithValidContext_ReturnsCommandInfoList test. This doesn't add meaningful test coverage for the hidden command filtering behavior.

        Assert.Contains(result, cmd => !string.IsNullOrEmpty(cmd.Name));

[anannya03]

While attempting to rebase my branch with main, I accidentally ran git push --force, which caused my original PR #796 to close.

I've since addressed all the review comments. For reference and better visibility, I’m including screenshots of each comment below:

5. I have run- dotnet format "AzureMcp.sln" for formatting errors.

[vcolin7]

The changes look good. You'll have to update the .vscode/cspell.json file to include the words flagged by the pipeline. Alternatively, you can remove those words from the PR. Up to you :)