Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_ses_get_cluster_server_images

Read-only

Retrieve available OS images for Search Engine Service G3 clusters, providing the image codes needed for cluster creation and configuration.

Instructions

Get available OS images for Search Engine Service (G3/KVM only). The returned image code is the softwareProductCode for ncloud_ses_get_server_specs, ncloud_ses_get_subnet_list_g3 and ncloud_ses_create_cluster_g3. For G2 use ncloud_ses_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 no safety red flags remain. The description adds valuable behavioral context beyond that: the G3/KVM restriction, the semantic relationship of the returned image code to downstream calls, and the G2 alternative. This meaningfully complements the 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences, no filler. Purpose is front-loaded, and the downstream-consumer detail and sibling routing each earn their place. Every sentence adds information an agent needs.

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 single-optional-parameter read-only lookup with no output schema, the description is nearly complete: it scopes the call, explains the returned value's role, and routes G2 users elsewhere. A minor gap is not describing the overall response shape, but given the annotation safety profile and simple input, this is a strong definition.

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?

Schema description coverage is 100% and the single parameter generationCode is fully documented with an enum and explanation. The description reinforces the G3-only constraint and adds the KVM-only qualifier, but this is minimal added value beyond the schema. Baseline 3 is appropriate.

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 verb ('Get'), a clear resource ('available OS images for Search Engine Service'), and an explicit scope ('G3/KVM only'). It also names the G2 alternative, so an agent can immediately distinguish this from ncloud_ses_get_os_products without inspecting schemas.

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 gives actionable routing guidance: use this for G3/KVM, and use ncloud_ses_get_os_products for G2. It also explains how the result will be consumed (as softwareProductCode for three downstream SES tools), which tells the agent when this lookup is needed.

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