Skip to main content
Glama
regru-cloud-mcp
by vl336

cloud_prices

Fetch hourly and monthly prices for Reg.Cloud resources and tariffs, including reglets, backups, IPs, licenses, and snapshots, to estimate cloud costs.

Instructions

Прайс-лист ресурсов Рег.облака: цена за час и за месяц для каждого тарифа/ресурса (reglet, backup, ip, license, snapshot).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cloud_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full load. It does disclose the payload shape (hourly and monthly prices per tariff and the resource types covered), and 'price list' implies a read-only, parameterless catalog. It does not state currency, whether prices are current or static, or whether any account context is required.

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?

One sentence, front-loaded with what the tool is, followed by the return units and the covered resource types. Nothing is padding; the parenthetical enumeration earns its place by telling the agent the coverage.

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 parameterless read-only lookup with no output schema, the description covers the essentials: what is returned, in what units, and for which resource types. Missing only minor context such as currency and price freshness.

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?

The tool takes zero parameters, so the baseline is 4. The description correctly implies the call is unfiltered and returns the whole catalog rather than a single resource's price.

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?

Names a specific resource (price list of Reg.cloud resources) and enumerates the units returned: hourly and monthly price per tariff/resource type (reglet, backup, ip, license, snapshot). An agent knows exactly what data this returns. It stops short of distinguishing itself from cloud_balance, which is the nearest sibling an agent could confuse it with.

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?

Usage is only implied by the name and content — 'price list' suggests cost lookup. There is no explicit statement of when to call it (e.g. cost estimation before provisioning) and no mention of the boundary with cloud_balance, which reports actual balance rather than catalog prices.

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