MCP Tools in Drills: Drill Start and Drill End

[dynamicdhx]

What does this PR do?

[Provide a clear, concise description of the changes]

[Add additional context, screenshots, or information that helps reviewers]

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
  • Created a changelog entry if the change falls among the following: new feature, bug fix, UI/UX update, breaking change, or updated dependencies. Follow the changelog entry guide
• 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
  • Validate README.md changes running the script ./eng/scripts/Process-PackageReadMe.ps1. See Package README
  • 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
  • For tools with new names, including new tools or renamed tools, update consolidated-tools.json
  • For renamed tools, follow the Tool Rename Checklist and tag the PR with the breaking-change label
  • For new tools associated with Azure services or publicly available tools/APIs/products, add URL to documentation in the PR description
• Extra steps for Azure MCP Server tool changes:
  • Updated command list in servers/Azure.Mcp.Server/docs/azmcp-commands.md
  • Ran ./eng/scripts/Update-AzCommandsMetadata.ps1 to update tool metadata in azmcp-commands.md (required for CI)
  • Updated test prompts in servers/Azure.Mcp.Server/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

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
There may be pipelines that require an authorized user to comment /azp run to run.

[dynamicdhx]

Tool Description Evaluator Results

Test 1

Expected Tool: resilience_drill_start
Prompt: Start resilience drill <drill_name> in service group <service_group> in Failover mode

Results

Rank	Score	Tool	Status
1	0.622278	resilience_drill_start	✅ EXPECTED
2	0.605322	resilience_drill_get	❌
3	0.565042	resilience_drill_end	❌
4	0.499669	resilience_drill_resource_get	❌
5	0.456094	resilience_recovery_plan_get	❌

---

Test 2

Expected Tool: resilience_drill_start
Prompt: Run resilience drill <drill_name> in service group <service_group> as a TestFailover

Results

Rank	Score	Tool	Status
1	0.617218	resilience_drill_start	✅ EXPECTED
2	0.581799	resilience_drill_get	❌
3	0.571091	resilience_drill_end	❌
4	0.503739	resilience_drill_resource_get	❌
5	0.453952	resilience_recovery_plan_delete	❌

Test 3

Expected Tool: resilience_drill_end
Prompt: End resilience drill <drill_name> in service group <service_group> with a Success attestation and notes "Validation completed"

Results

Rank	Score	Tool	Status
1	0.746492	resilience_drill_end	✅ EXPECTED
2	0.513245	resilience_drill_get	❌
3	0.489211	resilience_drill_start	❌
4	0.464825	resilience_drill_resource_get	❌
5	0.432815	resilience_recovery_plan_delete	❌

Test 4

Expected Tool: resilience_drill_end
Prompt: Stop the running resilience drill <drill_name> in service group <service_group> and attest it as Failed with notes "Validation failed"

Results

Rank	Score	Tool	Status
1	0.802001	resilience_drill_end	✅ EXPECTED
2	0.506002	resilience_drill_start	❌
3	0.500845	resilience_drill_get	❌
4	0.449067	resilience_recovery_plan_delete	❌
5	0.428687	resilience_drill_resource_get	❌