azure-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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_pricesA | Search Azure retail prices by service, region, SKU, or product name. Args: service_name: Azure service name (e.g. "Virtual Machines", "Storage") arm_region_name: Azure region (e.g. "eastus", "westeurope", "brazilsouth") arm_sku_name: ARM SKU name for exact match (e.g. "Standard_D8s_v5", "Standard_B2s") sku_name: SKU display name (e.g. "D2 v3", "Standard_LRS"). Use arm_sku_name for exact VM matching. product_name: Product name (e.g. "Virtual Machines Dv3 Series") price_type: Price type filter: "Consumption" (pay-as-you-go), "Reservation" (reserved instances), or "DevTestConsumption" currency_code: Currency code (default: USD). Examples: USD, EUR, BRL, GBP max_results: Maximum number of results to return (default: 10, max: 50) |
| estimate_costA | Estimate monthly cost for an Azure service based on quantity and usage hours. The estimation multiplies the unit retail price by the quantity and hours. For storage or data services priced per GB/month, set hours_per_month to 1. Args: service_name: Azure service name (e.g. "Virtual Machines") arm_sku_name: ARM SKU name for exact match (e.g. "Standard_D8s_v5") sku_name: SKU display name to narrow down (e.g. "D2 v3") arm_region_name: Azure region (e.g. "eastus") quantity: Number of units (e.g. VM instances, GB of storage). Default: 1 hours_per_month: Usage hours per month (default: 730 = 24/7). Set to 1 for flat monthly rates. currency_code: Currency code (default: USD) |
| compare_regionsA | Compare prices for an Azure service/SKU across multiple regions. Results are sorted by price (cheapest first). Args: service_name: Azure service name (e.g. "Virtual Machines") arm_sku_name: ARM SKU name for exact match (e.g. "Standard_D8s_v5") sku_name: SKU display name (e.g. "D2 v3") product_name: Product name for more specific filtering regions: List of region names to compare. If omitted, shows all available regions. currency_code: Currency code (default: USD) |
| list_servicesA | List available Azure services in the pricing API. Args: search: Optional text to filter service names (case-insensitive substring match) |
| list_regionsA | List available Azure regions. Args: service_name: If provided, only show regions where this service is available |
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 5 tools
Each tool has a clear, distinct purpose: searching prices, estimating costs, listing services, listing regions, and comparing regional prices. No two tools overlap in a way that would cause an agent to pick the wrong one.
All tool names follow a consistent verb_noun pattern with lowercase and underscores (search_prices, estimate_cost, list_services, list_regions, compare_regions). This makes the API predictable and easy to navigate.
With 5 tools, the server is well-scoped for its purpose. Each tool addresses a core aspect of Azure pricing: discovery, search, estimation, and regional comparison, without unnecessary redundancy.
The tool surface covers the main pricing workflow: discovering services and regions, searching for price data, comparing prices across regions, and estimating costs. No significant gaps are apparent for a read-only pricing API.