azure-vm-pricing-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_vm_sizesA | Find the cheapest Azure VM sizes that meet vCPU, memory and workload requirements, with monthly USD list prices. Burstable (B-series) and confidential sizes are only included when that workload is requested. |
| get_vm_sizeA | Specs of one Azure VM size and its hourly USD prices per region (Linux, Windows, 1/3-year reservations, 1/3-year savings plans), cheapest region first. |
| estimate_vm_costA | Monthly and yearly cost of one or more Azure VM sizes for pay as you go, reservations and savings plans, with the break-even hours per month for each commitment. Use it to compare sizes or regions. |
| get_price_changesA | Weekly report of new Azure VM sizes, retired sizes and the biggest list-price moves across 24 regions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct angle: find_vm_sizes discovers sizes meeting requirements, get_vm_size returns specs/hourly prices for one size, estimate_vm_cost computes committed monthly/yearly totals, and get_price_changes reports market movements. The main risk is overlap between get_vm_size (hourly prices) and estimate_vm_cost (monthly/yearly), but the descriptions make the intent distinguishable.
All four tools follow a clean verb_noun pattern (estimate_vm_cost, find_vm_sizes, get_vm_size, get_price_changes) with consistent snake_case and clear, standard verbs.
Four tools is a tight, well-scoped set for a VM pricing server — lookup, discovery, cost estimation, and change tracking — with no redundant entries. It is slightly on the thin side, but each tool clearly earns its place.
The surface covers the core pricing lifecycle: discovery by requirements, single-size detail, commitment cost comparison, and price-change monitoring. Minor gaps exist (e.g. no region/currency enumeration or discount/SKU availability lookup), but agents can work around them.