Skip to main content
Glama
Sign In
azure-vm-pricing-mcp

azure-vm-pricing-mcp

by vdionisopoulos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Find Azure VM sizes

find_vm_sizes
Read-only

Find Azure VM sizes matching vCPU, memory, GPU, or workload needs, with monthly USD list prices for cost comparison.

Instructions

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.

Input Schema

NameRequiredDescriptionDefault
osNoOperating system for pay-as-you-go prices. Default linux.
archNoCPU architecture.
sortNoprice = cheapest first (default); fit = least spare vCPU/memory first.
regionNoAzure region, e.g. westeurope or "West Europe". Omit to use each size's cheapest region.
min_gpusNoMinimum number of whole GPUs (partitioned GPUs such as 1/6 A10 do not count).
workloadNoWorkload family. ai = NVIDIA GPUs only (CUDA, PyTorch, vLLM); gpu = any GPU incl. AMD. Omit for any (excludes burstable and confidential).
min_vcpusNoMinimum vCPUs, e.g. 8.
max_resultsNoDefault 10.
min_memory_gibNoMinimum memory in GiB, e.g. 32.
need_temp_diskNoOnly sizes with a local temporary disk.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.1
    • changedInput schema / properties / min_gpus / maximum
      Previous value: -9007199254740991New value: +16
    • changedInput schema / properties / min_memory_gib / description
      Previous value: -"Minimum memory in GiB."New value: +"Minimum memory in GiB, e.g. 32."
    • addedInput schema / properties / min_memory_gib / maximum
      Added value: +32768
    • changedInput schema / properties / min_vcpus / description
      Previous value: -"Minimum vCPUs."New value: +"Minimum vCPUs, e.g. 8."
    • changedInput schema / properties / min_vcpus / maximum
      Previous value: -9007199254740991New value: +1024
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare readOnly/openWorld=false, so the description earns credit for disclosing non-obvious behavior: prices are monthly USD list prices, results are cheapest-first, and B-series/confidential sizes are filtered out by default. It says nothing about result-set size or what fields each size row carries, so it is not fully transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, no filler, front-loading the core search semantics before the caveat about burstable/confidential families.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter search tool with no output schema, the description covers the semantics an agent needs to choose it and interpret results (price basis, ordering, family exclusions). It omits any indication of the shape of the returned size records and result limiting beyond the schema's max_results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: the pricing model behind the numbers (monthly USD list, i.e. not reserved/spot) and the default cheapest-first ordering semantics. It does not elaborate on region fallback or gpu/vCPU interplay, so it does not reach 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (find) and resource (Azure VM sizes) plus the optimization criterion (cheapest meeting vCPU/memory/workload requirements) and the returned pricing basis. This clearly separates it from the singular get_vm_size/estimate_vm_cost siblings without needing to name them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives real selection guidance for the workload parameter: burstable and confidential families are only returned when explicitly requested, telling the agent how to obtain them. It never names the sibling alternatives or states when to prefer this over estimate_vm_cost, so it stops short of explicit when/when-not routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools