Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_cdss_get_cluster_server_images

Read-only

Retrieve available OS images for CDSS G3/KVM clusters. Returns image codes to use with server spec, subnet, and cluster creation APIs.

Instructions

Get available OS images for CDSS (G3/KVM). The returned image code is the softwareProductCode for ncloud_cdss_get_server_spec_list, ncloud_cdss_get_subnet_list_g3 and ncloud_cdss_create_cluster_g3. For G2 use ncloud_cdss_get_os_products.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
generationCodeNoServer generation code. Only G3 (3rd generation) is valid

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.15.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / generationCode
      Added value: +{
+  "description": "Server generation code. Only G3 (3rd generation) is valid",
+  "enum": [
+    "G3"
+  ],
+  "type": "string"
+}
  2. First observedv1.10.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds meaningful behavioral context beyond that: the scope is G3/KVM CDSS, and the returned image code doubles as the softwareProductCode for downstream tools. This goes beyond simple listing and helps the agent understand what the result represents.

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?

The description is three sentences with no fluff. The purpose is front-loaded, the downstream relationship is included in the second sentence, and the alternative tool is given in the third. Every sentence 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?

For a simple read-only tool with one optional enumerated parameter, the description is nearly complete: it states purpose, scope, downstream usage, and the G2 alternative. It does not describe the full return shape, but since no output schema exists, the note that the image code is the softwareProductCode partially fills that gap. The missing response details are a minor gap rather than a blocker.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents the only parameter generationCode with an enum of ['G3'] and a clear description, so schema coverage is 100%. The description adds context about G3 vs G2 but does not provide additional parameter-level semantics. The baseline 3 is appropriate because the schema carries the parameter documentation burden.

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 states a specific action ('Get available OS images') with a clear resource and scope ('CDSS (G3/KVM)'). It distinguishes itself from the related G2 path by explicitly routing that case to ncloud_cdss_get_os_products. This is enough for an agent to know exactly what this tool does and how it differs from alternatives.

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

Usage Guidelines5/5

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

The description provides an explicit usage boundary: use this for G3/KVM CDSS, and for G2 use ncloud_cdss_get_os_products. It also explains how the returned image code feeds into other CDSS tools, which clarifies the intended workflow context. No inference is required to decide when this tool is appropriate.

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

Deploy Server

Other Tools