Skip to main content
Glama
Sign In
Azure Pricing MCP Server

Azure Pricing MCP Server

by msftnadavbh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

azure_price_compare

Compare Azure service pricing across regions or SKUs to identify cost differences and optimize cloud spending.

Instructions

Compare Azure prices across regions or SKUs

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "service_name": "<service_name>"
    },
    "name": "azure_price_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
service_nameYesAzure service name to compare
sku_nameNoSpecific SKU to compare (optional)
regionsNoList of regions to compare (if not provided, compares SKUs)
currency_codeNoCurrency code (default: USD)USD
discount_percentageNoDiscount percentage to apply to prices (e.g., 10 for 10% discount). If not specified and show_with_discount is false, no discount is applied. If show_with_discount is true, defaults to 10%.
show_with_discountNoSet to true to apply a discount; uses default 10% unless discount_percentage is explicitly specified.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.3.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'compare' suggests a read-only operation, it doesn't clarify whether this queries live pricing APIs, cached data, or requires authentication. It also doesn't mention rate limits, data freshness, or what format the comparison results take.

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?

The description is a single, efficient sentence that immediately states the tool's core function. There's no wasted verbiage or unnecessary elaboration, making it easy for an agent to parse quickly.

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

Completeness2/5

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

For a 6-parameter tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the comparison output looks like, how results are structured, or provide context about data sources. The agent must rely entirely on the input schema without understanding the tool's behavior or results.

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

Parameters3/5

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

With 100% schema description coverage, the baseline is 3. The description adds minimal value beyond the schema, only implying that regions and SKUs are the comparison dimensions. It doesn't explain the relationship between regions and SKU parameters or provide examples of valid service/SKU names.

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

Purpose4/5

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

The description clearly states the tool's purpose as comparing Azure prices across regions or SKUs, which is a specific verb+resource combination. However, it doesn't explicitly differentiate this tool from its siblings like azure_price_search or azure_ri_pricing, which likely have overlapping price-related functionality.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With 12 sibling tools including azure_price_search, azure_ri_pricing, and azure_sku_discovery, the agent receives no help in selecting the appropriate price comparison tool for different scenarios.

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