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

cloud_ssh_keys

List SSH keys stored in Reg.ru Cloud to view their names, fingerprints, and public keys for access management.

Instructions

Список SSH-ключей, загруженных в Рег.облако: имя, отпечаток (fingerprint), публичный ключ.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It implies a read-only listing but does not state whether results are paginated, scoped to the caller's account/project, or whether authentication is required; nor does it mention ordering or limits.

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 compact sentence with the resource front-loaded and the returned fields appended; nothing is wasted. It is short to the point of omitting usage context.

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

Completeness3/5

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

For a no-parameter list operation with no output schema and no annotations, the description covers what the tool returns but not the operational context (scope, pagination, permissions). Adequate but with clear gaps.

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 parameter semantics are moot and the baseline is 4. The description's field enumeration (name, fingerprint, public key) actually helps set expectations about the response shape.

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 states a specific resource and action: listing SSH keys uploaded to Рег.облако, and enumerates the returned fields (name, fingerprint, public key). That distinguishes it from siblings like cloud_servers or cloud_snapshots, though it never explicitly says it is read-only or how it differs from any key-management sibling.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives among the sibling tools. The agent must infer that this is the right tool whenever SSH keys are of interest.

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