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

cloud_snapshots

Lists Reg.ru Cloud snapshots with name, size, base image, required deployment disk, and creation date to help you inspect available images before provisioning.

Instructions

Список снэпшотов Рег.облака: имя, размер (size_gigabytes), базовый образ (distribution), минимальный диск для развёртывания, дата создания.

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

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 burden: it does disclose what the tool returns (field names and meanings), which usefully implies a read-only, non-destructive operation. It says nothing about authentication requirements, pagination, ordering, or emptiness behavior, which is a real gap given zero annotation coverage.

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 front-loaded sentence naming the resource followed by a compact enumeration of returned fields; no filler. The dense parenthetical field list is slightly clipped but every element earns its place.

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 parameters and no output schema, the description's field enumeration is exactly what is needed to tell an agent what comes back. Only the absence of auth/pagination or read-safety information keeps it short of complete.

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 no parameters, so per the baseline this scores 4. The description correctly implies a global listing with no filtering options, matching the empty schema.

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 concrete verb and resource — listing Reg.cloud snapshots — and even enumerates the fields returned (name, size_gigabytes, distribution, minimum disk, creation date). It is clearly distinct from the sibling tools (balance, prices, servers, ssh keys), though it does not explicitly say so.

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 imperative 'list snapshots'; there is no statement of when to call this versus cloud_server or cloud_servers, and no prerequisites or exclusions are given. For a zero-parameter listing tool this is adequate but leaves the agent to infer context.

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