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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_nks_get_kubeconfig

Read-only

Retrieve the kubeconfig for an NKS cluster by providing its UUID, enabling direct access to the cluster.

Instructions

Retrieve the kubeconfig for a specified NKS cluster

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": {
      "clusterUuid": "<clusterUuid>"
    },
    "name": "ncloud_nks_get_kubeconfig"
  }
}

Input Schema

NameRequiredDescriptionDefault
clusterUuidYesUUID of the cluster

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A3.6/5.0
Behavior2/5

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

The description adds no behavioral context beyond the readOnlyHint annotation. It does not disclose what the kubeconfig response contains, authentication requirements, or any other operational details. The annotation already communicates that this is a safe read operation, so the description contributes little additional transparency.

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 one sentence of ten words, front-loaded with the action ('Retrieve') and the resource ('kubeconfig'), making it concise and immediately parsable with no wasted words.

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 getter with one parameter and a read-only annotation, the description is adequate. It could have mentioned the kubeconfig content or return format, but given the low complexity and the useful annotation, it is reasonably complete.

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 fully documents the single parameter (clusterUuid with description 'UUID of the cluster'), so the schema coverage is 100%. The description's reference to 'a specified NKS cluster' mirrors the schema without adding new semantic detail. Baseline of 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 uses the specific verb 'Retrieve' and clearly identifies the resource as the kubeconfig for an NKS cluster. This distinguishes it from sibling tools like ncloud_nks_reset_kubeconfig (which resets) and ncloud_nks_get_cluster (which gets cluster info).

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 does not explicitly state when to use this tool versus alternatives or mention any prerequisites. Usage is implied by the tool's name and straightforward retrieval purpose, but no explicit guidance is provided.

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