Azure Pricing MCP Server

azure_ri_pricing

Calculate Azure Reserved Instance pricing and savings by comparing with on-demand rates for specific services, SKUs, and regions to optimize cloud costs.

Instructions

Get Reserved Instance pricing and savings analysis

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_ri_pricing"
  }
}

Input Schema

Name	Required	Description	Default
`service_name`	Yes	Azure service name (e.g., 'Virtual Machines')
`sku_name`	No	SKU name (e.g., 'D4s v3')
`region`	No	Azure region (e.g., 'eastus')
`reservation_term`	No	Reservation term ('1 Year' or '3 Years')
`currency_code`	No	Currency code (default: USD)	USD
`compare_on_demand`	No	Compare with On-Demand prices to calculate savings (default: true)
`limit`	No	Maximum number of results (default: 50)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.3.0Feb 25, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Get' implies a read-only operation, it doesn't specify whether this requires authentication, has rate limits, returns paginated results, or provides detailed savings breakdowns. For a tool with 7 parameters and no annotation coverage, this is a significant gap in behavioral context.

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 front-loads the core purpose without unnecessary words. It's appropriately sized for the tool's complexity, with every part contributing directly to understanding what the tool does.

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?

Given the tool's complexity (7 parameters, no annotations, no output schema), the description is incomplete. It lacks guidance on usage relative to siblings, behavioral details like authentication or rate limits, and any indication of return format or error handling. This leaves significant gaps for an agent to invoke the tool correctly in context.

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?

The description adds no parameter-specific information beyond what's already in the input schema, which has 100% coverage with detailed descriptions for all 7 parameters. The baseline score of 3 reflects that the schema adequately documents parameters, but the description doesn't enhance understanding with additional context like typical use cases or parameter interactions.

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 with a specific verb ('Get') and resource ('Reserved Instance pricing and savings analysis'), making it immediately understandable. However, it doesn't explicitly differentiate this tool from its siblings like 'azure_price_compare' or 'azure_price_search', which might have overlapping 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 multiple sibling tools related to Azure pricing and SKUs (e.g., 'azure_price_compare', 'azure_discover_skus'), there's no indication of context, prerequisites, or exclusions to help an agent choose appropriately.

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

Deploy Server