Skip to main content
Glama
Sign In
ncloud-gov-mcp-server

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_nks_get_server_specs

Read-only

List available server specifications for NKS cluster or node pool creation. Provide softwareCode and zoneCode or zoneNo to view compatible options.

Instructions

List available server specifications for NKS cluster/node pool creation. Requires softwareCode (from ncloud_nks_get_server_images) and zoneCode or zoneNo.

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": {
      "softwareCode": "<softwareCode>"
    },
    "name": "ncloud_nks_get_server_specs"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoneNoNoZone number. Required if zoneCode not provided.
zoneCodeNoZone code (e.g., KR-1). Required if zoneNo not provided.
softwareCodeYesServer image code (value from ncloud_nks_get_server_images)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4/5.0
Behavior3/5

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

The readOnlyHint annotation is consistent with the 'List' action, and the description adds valuable context about the dependency on ncloud_nks_get_server_images. However, it does not disclose potential response format, pagination, or other behavioral traits beyond the annotation.

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?

Two sentences, front-loaded with the core purpose, no filler or redundant information. Every word 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 list tool with full schema coverage and a read-only annotation, the description is adequate. It clearly states purpose and prerequisites. It could optionally mention the return value (list of server specifications), but the tool name and nature make this obvious.

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 input schema already documents all parameters with descriptions, achieving 100% coverage. The description adds minimal extra meaning, mostly repeating the dependency on ncloud_nks_get_server_images and the zoneCode/zoneNo mutual requirement already present in the schema.

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 clearly states what the tool does: 'List available server specifications for NKS cluster/node pool creation.' It uses a specific verb ('List'), identifies the resource ('server specifications'), and scopes it to NKS cluster/node pool creation, distinguishing it from sibling tools like ncloud_get_server_specs or ncloud_ses_get_server_specs.

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?

The description provides clear usage context by stating this is for NKS cluster/node pool creation and listing required prerequisites (softwareCode from ncloud_nks_get_server_images and zoneCode or zoneNo). However, it does not explicitly mention when not to use it or name alternative tools.

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