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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_nks_get_available_addon_version

Read-only

Get configuration schema and details for a specific add-on version. Provide addon name, version, and Kubernetes version (1.36+) to retrieve configurationValues.

Instructions

Get details of a specific add-on version (Add-on Manager catalog; requires Kubernetes 1.36+), including its configuration schema for configurationValues.

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": {
      "addonName": "<addonName>",
      "version": "<version>",
      "k8sVersion": "<k8sVersion>"
    },
    "name": "ncloud_nks_get_available_addon_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionYesAdd-on version (from ncloud_nks_get_available_addon)
addonNameYesAdd-on name
k8sVersionYesKubernetes version in major.minor.patch (e.g., 1.36.0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true. The description adds that it returns configuration schema and requires K8s 1.36+, which provides some additional context but does not substantially expand behavioral disclosure 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?

Single sentence with all essential information: purpose, constraints (K8s 1.36+), and output hint (configuration schema). No fluff or redundancy.

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?

The tool has 3 required parameters and no output schema. The description hints at the return content (configuration schema) and notes a key constraint. While not exhaustive, it covers the main points adequately for a simple get operation.

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?

Input schema has 100% coverage of parameter descriptions. The description does not add further parameter-specific meaning beyond what the schema already provides. 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 explicitly states 'Get details of a specific add-on version' and mentions the inclusion of configuration schema. It distinguishes from siblings like ncloud_nks_get_available_addon by focusing on a version, not just an add-on.

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?

The description mentions a prerequisite (Kubernetes 1.36+) but does not explicitly guide when to use this tool vs alternatives like ncloud_nks_get_available_addon. Usage is implied rather than clearly stated.

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