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

cloud_servers

Lists all Reg.ru Cloud VPS instances with status, OS, plan, CPU, memory, disk, IPs, PTR, region, backups, and creation date to support inventory and monitoring.

Instructions

Список всех облачных серверов (VPS) Рег.облака: имя, статус (new/active/off/suspended/archive), ОС (image), тариф (size), CPU (vcpus), память (memory, МБ), диск (disk, ГБ), IPv4/IPv6, PTR, регион, включены ли бэкапы, дата создания.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 behavioral burden. It usefully discloses the returned attributes (status values, units for memory in MB and disk in GB, backup flag, PTR, region), but says nothing about result volume, pagination, auth requirements, or whether the listing is filtered by account scope.

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?

One front-loaded sentence: purpose first, then the field inventory. The long enumeration earns its place because no output schema exists, though the parenthetical unit annotations could be tightened.

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?

With no output schema and no annotations, the description is the only source of return-value information, and it covers that well, including the status enum values. The remaining gap is operational: nothing about how many servers come back or whether the call is safe to repeat.

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, which sets the baseline at 4; there is no parameter semantics for the description to add. The enumerated field list instead compensates on the output side.

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 gives a specific verb and resource ("Список всех облачных серверов (VPS) Рег.облака") and follows it with the exact field set returned. The word "всех" implicitly separates it from the singular sibling cloud_server, but that contrast is never made explicit.

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?

The description says it returns ALL servers and lists the fields, which implies this is the enumeration/overview tool rather than a detail lookup. It never names cloud_server as the alternative for a single server, and says nothing about when the field set is not needed.

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