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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_nks_list_available_addons

Read-only

Specify a Kubernetes version to list installable NKS add-ons, including ExternalDNS and Istio, for cluster customization.

Instructions

List add-ons installable on an NKS cluster for a given Kubernetes version (Add-on Manager catalog; Add-on Manager is only available on Kubernetes 1.36+ clusters). Requires k8sVersion. The catalog includes components delivered as add-ons such as the NAVER Cloud Global DNS (ExternalDNS) webhook provider and, since 2026-09-17, Istio (service mesh); the available add-ons vary by Kubernetes version and region.

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": {
      "k8sVersion": "<k8sVersion>"
    },
    "name": "ncloud_nks_list_available_addons"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for pagination
sizeNoPage size for pagination
k8sVersionYesKubernetes version in major.minor.patch (e.g., 1.36.0). Use the version from ncloud_nks_get_versions without the -nks.N suffix

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations carry readOnlyHint=true, which the description aligns with. Beyond the annotation, it adds meaningful behavioral context: the 1.36+ availability constraint, that results vary by Kubernetes version and region, and concrete catalog contents (ExternalDNS, Istio since 2026-09-17). No contradiction with annotations; the description adds value beyond what annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Two information-dense sentences with the purpose front-loaded, but the text is a bit cluttered: 'Requires k8sVersion' repeats the schema, and the Istio date ('since 2026-09-17') is a niche detail that could be trimmed. Every fragment mostly earns its place, but the structure could be cleaner.

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 3-param tool with no output schema, the description conveys purpose, required parameter, availability constraint, content examples, and variation factors. The main gap is the absence of return-value description (since there is no output schema), but for a list catalog the return shape is fairly evident. Reasonably complete overall.

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 coverage is 100% and the k8sVersion description is already detailed (including guidance to strip the -nks.N suffix). The description adds minor interpretive value by noting the catalog varies by version and region, and it redundantly restates 'Requires k8sVersion' which the schema's required array already conveys. Baseline 3 is appropriate since the schema carries the parameter burden.

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?

States a specific verb+resource: 'List add-ons installable on an NKS cluster for a given Kubernetes version'. The word 'installable' plus 'Add-on Manager catalog' implicitly distinguishes this from siblings like ncloud_nks_list_cluster_addons (installed add-ons), but it does not explicitly name any sibling. Clear and specific, though differentiation is implicit rather than stated.

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?

Provides some when-to-use context: 'Add-on Manager is only available on Kubernetes 1.36+ clusters' tells an agent when this catalog exists, and 'Requires k8sVersion' flags the dependency. However, it offers no explicit alternatives or exclusions (e.g., 'for installed add-ons on a cluster use ncloud_nks_list_cluster_addons'). Usage context is implied but not fully developed.

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