Azure Pricing MCP Server

azure_discover_skus

Find available SKUs for Azure services to compare pricing and features across regions, helping users select the right configuration for their needs.

Instructions

Discover available SKUs for a specific Azure service

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

Input Schema

Name	Required	Description	Default
`service_name`	Yes	Azure service name
`region`	No	Azure region (optional)
`price_type`	No	Price type (default: 'Consumption')	Consumption
`limit`	No	Maximum number of SKUs to return (default: 100)

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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool discovers SKUs but doesn't mention whether this is a read-only operation, if it requires authentication, rate limits, or what the output format looks like. For a tool with 4 parameters and no output schema, this leaves significant behavioral gaps.

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 gets straight to the point without any wasted words. It's appropriately sized for the tool's complexity and front-loaded with the core purpose.

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 has 4 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what SKUs are, how results are structured, or provide context about Azure service naming conventions. For a discovery tool with multiple siblings, more contextual information would be helpful.

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?

Schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description doesn't add any meaningful parameter semantics beyond what's in the schema (e.g., explaining what 'SKUs' are or how they relate to Azure services). The baseline of 3 is appropriate when the schema does the heavy lifting.

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 action ('discover') and resource ('available SKUs for a specific Azure service'), making the purpose immediately understandable. However, it doesn't explicitly distinguish this tool from its sibling 'azure_sku_discovery', which appears to serve a similar function based on the name alone.

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 like 'azure_sku_discovery' or other Azure pricing-related siblings. It mentions a specific Azure service context but offers no exclusions, prerequisites, or comparison with other tools in the server.

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

Deploy Server