Crypto, web, finance and app data tools

Azure VM Prices

azure_vm_prices

Azure retail prices for a VM SKU (e.g. Standard_D4s_v5, Standard_NC24ads_A100_v4) in one region or all regions: Linux and Windows pay-as-you-go, spot and 1/3-year reserved hourly rates, cheapest region first.

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": {
      "sku": "<sku>"
    },
    "name": "azure_vm_prices"
  }
}

Input Schema

Name	Required	Default
`sku`	Yes
`region`	No	eastus
`service`	No	Virtual Machines

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 24, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations, so the description carries the behavioral burden. It usefully discloses the returned pricing dimensions (Linux/Windows PAYG, spot, 1/3-year reserved) and ordering ('cheapest region first'), but omits data source/freshness, auth needs, and rate-limit behavior for a live pricing lookup.

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

Conciseness4/5

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

A single dense sentence that front-loads the core purpose and enumerates the valuable pricing dimensions with zero filler. Slightly long but every clause adds information.

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?

An output schema exists, so return-format description is unnecessary. For a 3-param, 1-required tool this is largely complete, though the undocumented `service` parameter and the 'all regions' mechanics leave minor gaps.

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 coverage is 0%, so the description must compensate. It does well for `sku` (two concrete examples) and explains `region` behavior ('one region or all regions'), but the `service` parameter is never mentioned and the 'all regions' invocation semantics are unclear.

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?

The description states a specific verb and resource (Azure retail VM prices for a SKU), with concrete example SKUs and pricing types. 'Azure' cleanly distinguishes this from siblings like aws_ec2_prices and gpu_rental_prices without ambiguity.

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

Usage Guidelines3/5

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

It implies usage context (one region or all regions, cheapest region first) but never states when to prefer this over aws_ec2_prices or gpu_rental_prices, nor any prerequisites or exclusions. Guidance is inferred rather than explicit.

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

All Crypto, web, finance and app data tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?