Nearly all MCP tools are merely LLM-friendly APIs for existing product features. The remainder of the MCP tools use duct tape to fix the crappy code in the existing product so that the LLM can't overwrite your boot sector when it runs the MCP tool.
The Pylance extension tool "pylanceRunCodeSnippet", however, is a bona fide MCP Tool.
I got my first internet job in 1996 at what is now CBS Sportsline. I bought my first smartphone in 2000 (not a typo: the year two-thousand). I've seen a few technological innovations, you know? Of the MCP interfaces I use, Pylance's "pylanceRunCodeSnippet" is the first true MCP tool I have seen instead of a repackaged product.
I strongly suspect Microsoft started the creation of "pylanceRunCodeSnippet" to try to fix the "Copilot cannot read the Copilot terminal" problem, but the team that worked on the issue put the duct-tape on the shelf and made an innovative tool.
In a couple of years, this kind of innovation will be common--because tons of people will know what path to travel when creating an MCP tool.
In contrast, this team created a bona fide MCP tool without project templates or checklists. I've long said, "The hardest part of being a trailblazer is that, by definition, there are no maps."
Nearly all MCP tools are merely LLM-friendly APIs for existing product features. The remainder of the MCP tools use duct tape to fix the crappy code in the existing product so that the LLM can't overwrite your boot sector when it runs the MCP tool.
The Pylance extension tool "pylanceRunCodeSnippet", however, is a bona fide MCP Tool.
I got my first internet job in 1996 at what is now CBS Sportsline. I bought my first smartphone in 2000 (not a typo: the year two-thousand). I've seen a few technological innovations, you know? Of the MCP interfaces I use, Pylance's "pylanceRunCodeSnippet" is the first true MCP tool I have seen instead of a repackaged product.
I strongly suspect Microsoft started the creation of "pylanceRunCodeSnippet" to try to fix the "Copilot cannot read the Copilot terminal" problem, but the team that worked on the issue put the duct-tape on the shelf and made an innovative tool.
In a couple of years, this kind of innovation will be common--because tons of people will know what path to travel when creating an MCP tool.
In contrast, this team created a bona fide MCP tool without project templates or checklists. I've long said, "The hardest part of being a trailblazer is that, by definition, there are no maps."