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

cloud_balance

Check remaining Reg.ru Cloud funds and bonuses, see hourly and monthly spend, estimate days or hours left, and inspect per-resource cost breakdown.

Instructions

Баланс Рег.облака (Reg.ru Cloud): остаток денег и бонусов, hourly_cost/monthly_cost — сколько списывают все ресурсы за час и за месяц, days_left/hours_left — на сколько хватит средств, и detalization — детализация: какой ресурс сколько потребляет (серверы, бэкапы, IP и т.д.).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the returned figures (balance, bonuses, hourly_cost, monthly_cost, days_left, hours_left, detalization), telling the agent this is a read-only financial snapshot. It does not mention currency, refresh cadence, or whether detalization is always included, but nothing is misleading.

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, front-loaded with the identity (cloud balance) followed by the field meanings. It is list-like but every clause maps to a returned value, so little is wasted; a shorter framing plus a bulleted field list would read slightly better.

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

Completeness5/5

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

There is no output schema and no parameters, so the description must explain the return values, and it enumerates each one with plain-language meaning. For a zero-arg read-only balance check, an agent has everything needed to call it and interpret the result.

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 there is no parameter meaning to add; baseline 4 applies. The description instead spends its words on return semantics, which is the right use of space here.

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 names the concrete resource (Reg.ru Cloud balance) and enumerates exactly what it reports: remaining money and bonuses, hourly/monthly cost, days_left/hours_left, and per-resource detalization. This makes it clearly separable from siblings like cloud_prices (pricing) or cloud_server (a single server) without needing their schemas.

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: an agent can infer this is the tool to call when it wants to know remaining funds or burn rate. There is no explicit when-to-use / when-not guidance (e.g., versus cloud_prices for rate lookups) and no stated prerequisites.

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