1# MCP tools used by vm-creator
2 
3The Azure MCP server exposes the `compute` area as a single namespace proxy: `mcp__azure__compute({intent, command, parameters})`. The commands below are what the workflow dispatches against it.
4 
5## Read-only validation (Step 4)
6 
7| Command | Purpose | Key parameters |
8|---|---|---|
9| `compute_vm_list-skus` | Confirm SKU availability + filter by vCPU/memory/family | `subscription`, `location`, `minVCpus`, `minMemoryGb`, `familyPrefix`, `top` |
10| `compute_vm_list-images` | Resolve image alias / URN | `subscription`, `location`, `publisher`, `offer`, `sku` |
11| `compute_vm_check-quota` | Verify vCPU headroom for the family | `subscription`, `location`, `family` |
12| `compute_vm_recommend-region` | Find regions where the workload fits | workload hints; returns ranked regions |
13 
14## Apply (Step 6, Adapter 4)
15 
16| Command | Purpose |
17|---|---|
18| `compute_vm_create` | Create a single VM from Plan Card fields |
19| `compute_vmss_create` | Create a VMSS (adds `instance-count`, `upgrade-policy`) |
20| `compute_vm_get` | Inspect after create |
21| `compute_vm_update` | Tag changes, size resize, identity attach |
22| `compute_vm_delete` | Cleanup |
23 
24See [output-adapters/mcp-apply.md](output-adapters/mcp-apply.md) for the full parameter mapping and failure-handling table.
25 
26## CLI fallbacks (when Azure MCP is not connected)
27 
28| MCP command | CLI equivalent |
29|---|---|
30| `compute_vm_list-skus` | `az vm list-skus --location <region> --output table` |
31| `compute_vm_list-images` | `az vm image list --location <region> --offer <offer> --all` |
32| `compute_vm_check-quota` | `az vm list-usage --location <region> --output table` |
33| `compute_vm_recommend-region` | (no CLI equivalent — fall back to docs) |
34| `compute_vm_create` | `az vm create ...` (see [az-cli.md](output-adapters/az-cli.md)) |
35 
36## Why the proxy form matters
37 
38The CLI / tool host shows `mcp__azure__compute` as a single tool. Sub-operations like `vm check-quota`, `vm list-skus`, etc. are not separate tools — they are passed through the `command` parameter. Every command is invoked as:
39 
40```
41mcp__azure__compute({
42  command: "vm check-quota",
43  parameters: { location: "eastus", family: "standardDSv5Family" }
44})
45```
46 
47When tracing tool calls or writing must-call rubrics, look for the `command=` argument, not a distinct tool name.
48