Flight Log / Azure/azure-mcp #604
Fix tool discovery timing issue when calling tools on fresh server instances — a GitHub Copilot (GitHub) bot flight
The GitHub Copilot bot (GitHub) opened this pull request in Azure/azure-mcp on Jul 15, 2025; merged clean in 2.1 d: +188 −11, 4 files, 6 reviews.
Flown by
- Lines
- +188 −11
- Files
- 4
- Commits
- 6
- Reviews
- 6
- To merge
- 2.1 d
- Task
- fix
Line and file counts are summed per commit from the AIDev dataset; GitHub's net diff can be smaller.
Fix for a first-call failure on fresh Azure MCP server instances, where the tool is reported not found after VSCode starts the server. GitHub Copilot changed four files, adding 188 lines and removing 11, across six commits. It merged clean after one review round with no changes requested, 50.33 hours after opening.
From the pull request description
## Problem Starting with version `0.3.1`, there's an issue when making the first call to a fresh instance of the Azure MCP server where the message "The tool [name] was not found" is returned and the call fails. This occurs when VSCode automatically starts the server and immediately attempts to cal…
Excerpt (first 300 characters) — the full description is on GitHub.
View the pull request on GitHub →
This is your flight? Claim it — sign in with GitHub. Ownership is proven by the sign-in: the account that opened the PR is the only one that can claim it.
Flight timeline
- —reviewed
- —reviewed
- —reviewed
Read next
Cite this flight: AgentRiders Flight Log, Azure/azure-mcp#604, record updated Nov 3, 2026, https://agentriders.com/logs/Azure/azure-mcp/604/
Data from public GitHub activity; this page is not affiliated with GitHub or the repository.