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

cloud_server

Fetches detailed configuration, status, OS, IP address, and actual disk usage for a specific Reg.ru Cloud server using its ID.

Instructions

Подробная информация об одном сервере по id (id взять из cloud_servers): конфигурация, статус, ОС, IP, фактическое использование диска (disk_usage) и т.д.

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": {
      "id": "<id>"
    },
    "name": "cloud_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesИдентификатор сервера (поле id из cloud_servers)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It partially discharges this by detailing what data is returned (configuration, status, OS, IP, disk_usage), which compensates for the missing output schema. However, it says nothing about whether the tool is strictly read-only, what happens for an invalid/nonexistent id, or any permission requirements, leaving real 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?

A single front-loaded sentence with no wasteful wording; the most important scoping constraint (single server by id, sourced from cloud_servers) appears first, followed by the returned fields.

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 one-parameter lookup tool with no output schema, the description lists the key returned fields, giving the agent enough to decide and call correctly. The trailing "и т.д." (etc.) leaves the return shape slightly open, but overall it is complete for this tool's complexity.

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?

Schema coverage is 100%, so the baseline would be 3. The description adds meaning beyond the schema by specifying the provenance constraint on id (must come from cloud_servers), which is a genuine semantic rule the schema does not encode.

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 opens with a specific verb+resource: "Подробная информация об одном сервере по id" (detailed info about a single server by id). It also enumerates the returned facets (configuration, status, OS, IP, disk_usage), so an agent instantly distinguishes this single-server lookup from the sibling list tool cloud_servers.

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

Usage Guidelines4/5

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

It explicitly tells the agent where the id comes from: "id взять из cloud_servers", establishing the list-then-detail workflow and implicitly separating this tool from the list tool. It does not spell out when it should NOT be used or name other alternatives, so it falls short of full 5-level routing guidance.

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