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 has a distinct primary purpose: change reporting, single-size lookup, requirement-based discovery, and multi-size cost projection. However, get_vm_size (per-region hourly prices), find_vm_sizes (monthly list prices), and estimate_vm_cost (monthly/yearly costs with commitments) all surface pricing data, so an agent could reasonably confuse which pricing tool to pick for a given question.
All four names follow a clean verb_noun snake_case pattern (get_price_changes, get_vm_size, find_vm_sizes, estimate_vm_cost). Verb choices (get/find/estimate) are predictable and the singular/plural distinction between get_vm_size and find_vm_sizes is semantically meaningful, not inconsistent.
Four tools is slightly lean but well-scoped for a narrow domain like Azure VM pricing: monitoring, lookup, search, and estimation. Nothing redundant, though a slightly broader surface (e.g., a catalog/region listing tool) would round it out.
The surface covers the core pricing lifecycle: change tracking, per-size specs and regional prices, requirement-based discovery, and commitment cost estimation with break-even analysis. Gaps are minor (no spot/preemptible pricing, no full catalog or region listing), but agents can work around them with the existing tools.