Add build_bicep and build_bicepparam tools to the MCP server

[Copilot]

The MCP server lacked dedicated tools for compiling Bicep files and returning the compiled output. This PR replaces get_bicep_file_diagnostics with two dedicated build tools that both compile and return results.

Changes

• Two new MCP tools in BicepCompilerTools:
  • build_bicep — compiles a .bicep file via compilation.Emitter.Template(), returns { success, template, diagnostics }
  • build_bicepparam — compiles a .bicepparam file via compilation.Emitter.Parameters(), returns { success, parameters, template, diagnostics }
• Removed get_bicep_file_diagnostics — superseded by the new build tools, which already include diagnostics in their responses
• Shared helper GetDiagnostics() extracted to avoid duplicating the diagnostic projection logic
• New result records BuildBicepResult and BuildBicepparamResult with inline [Description] annotations for MCP schema generation
• Unit tests for both tools covering successful compilation and error cases
• tools.json baseline updated to reflect the tool changes

Example

// main.bicep
param location string = 'westus'
output loc string = location

Calling build_bicep returns:

{
  "success": true,
  "template": "{ \"$schema\": \"...\", ... }",
  "diagnostics": []
}

On error, success is false, template/parameters is null, and diagnostics contains the full error list.

[anthony-c-martin]

@copilot remove this tool, it's not needed any more

[Copilot]

Done in 03f962a. Removed GetBicepFileDiagnostics and its associated test, and updated the Error_filter_returns_error_information test in ServerTests.cs to use build_bicep instead.

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• aka.ms
  • Triggering command: /usr/share/dotnet/dotnet /usr/share/dotnet/dotnet exec /home/REDACTED/work/bicep/bicep/src/Bicep.McpServer.UnitTests/bin/Debug/net10.0/Bicep.McpServer.UnitTests.dll --internal-msbuild-node /tmp/297b29e2a27a49a0b72bc809034ff974/.p --ignore-exit-code 8 --test-parameter SetBaseLine=true (dns block)
• westcentralus.data.mcr.microsoft.com
  • Triggering command: /usr/share/dotnet/dotnet /usr/share/dotnet/dotnet exec /home/REDACTED/work/bicep/bicep/src/Bicep.McpServer.UnitTests/bin/Debug/net10.0/Bicep.McpServer.UnitTests.dll --internal-msbuild-node /tmp/297b29e2a27a49a0b72bc809034ff974/.p --ignore-exit-code 8 --test-parameter SetBaseLine=true (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[github-actions]

Test this change out locally with the following install scripts (Action run 25416326898)

VSCode

• Mac/Linux

  bash <(curl -Ls https://aka.ms/bicep/nightly-vsix.sh) --run-id 25416326898

• Windows

  iex "& { $(irm https://aka.ms/bicep/nightly-vsix.ps1) } -RunId 25416326898"

Azure CLI

• Mac/Linux

  bash <(curl -Ls https://aka.ms/bicep/nightly-cli.sh) --run-id 25416326898

• Windows

  iex "& { $(irm https://aka.ms/bicep/nightly-cli.ps1) } -RunId 25416326898"