Add in-memory content support to build_bicep, build_bicepparam, and format_bicep_file

[Copilot]

build_bicep (the renamed diagnostics tool) and format_bicep_file previously required on-disk files, which made LLM-generated, in-memory Bicep flows awkward. This change adds first-class in-memory payload support and brings build_bicepparam to parity.

• MCP compiler/formatter input model

  • Updated build_bicep, build_bicepparam, and format_bicep_file to accept optional content alongside filePath.
  • Supported call modes:
    • filePath only: existing disk-based behavior.
    • content only: compile/format entirely in-memory.
  • Added validation to reject ambiguous input when both filePath and content are provided.

• Compilation path changes

  • Added shared compilation helper in BicepCompilerTools that:
    • validates minimum input (filePath or content required),
    • validates mutual exclusivity (filePath and content cannot both be provided),
    • preserves extension/type checks,
    • creates an in-memory workspace entry when content is supplied.

• Tool contract and discoverability

  • Updated MCP tool descriptions and JSON schemas (tools.json) to document one-or-the-other input semantics.
  • Updated docs to reflect current tool naming (build_bicep) and in-memory support, including build_bicepparam.

• Focused coverage updates

  • Added/updated unit tests for:
    • in-memory formatting,
    • in-memory build_bicep,
    • in-memory diagnostics behavior for build_bicepparam,
    • validation when both filePath and content are provided.

// in-memory bicep build
var result = await tools.BuildBicep(content: """
param location string = 'westus'
output loc string = location
""");

// path-based bicepparam build
var result2 = await tools.BuildBicepparam("/repo/main.bicepparam");

> [!WARNING]
>
>

[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: /tmp/dotnet-10.0.300/dotnet /tmp/dotnet-10.0.300/dotnet exec /home/REDACTED/work/bicep/bicep/src/Bicep.McpServer.UnitTests/bin/Debug/net10.0/Bicep.McpServer.UnitTests.dll --internal-msbuild-node /tmp/717ad653bc70455ab94f7768b1e51d88/.p --ignore-exit-code 8 --filter FullyQualifiedName~Bicep.McpServer.UnitTests.BicepCompilerToolsTests (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)