Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_nks_create_access_entry

Create an IAM access entry for an NKS cluster, mapping an IAM user or role to Kubernetes groups or NKS access policies.

Instructions

Create an IAM access entry for an NKS cluster: maps an IAM USER or ROLE (NRN) to Kubernetes groups and/or NKS access policies. Requires authType=API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesIAM principal type
entryYesNRN of the IAM USER or ROLE
groupsNoKubernetes group names to bind the principal to
policiesNoNKS access policies to attach (type + scope, namespaces when scope is 'namespace')
clusterUuidYesUUID of the cluster

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv2.0.1
    • addedInput schema / properties / entry
      Added value: +{
+  "description": "NRN of the IAM USER or ROLE",
+  "type": "string"
+}
    • addedInput schema / properties / groups
      Added value: +{
+  "description": "Kubernetes group names to bind the principal to",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • removedInput schema / properties / kubernetesGroups
      Removed value: -{
-  "description": "Kubernetes groups",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
    • addedInput schema / properties / policies
      Added value: +{
+  "description": "NKS access policies to attach (type + scope, namespaces when scope is 'namespace')",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "namespaces": {
+        "description": "Target namespaces — required when scope is 'namespace'",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "scope": {
+        "description": "Policy scope",
+        "enum": [
+          "cluster",
+          "namespace"
+        ],
+        "type": "string"
+      },
+      "type": {
+        "description": "NKS access policy type",
+        "enum": [
+          "NKSClusterAdminPolicy",
+          "NKSAdminPolicy",
+          "NKSEditPolicy",
+          "NKSViewPolicy"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "scope"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • removedInput schema / properties / principalArn
      Removed value: -{
-  "description": "IAM principal ARN",
-  "type": "string"
-}
    • changedInput schema / properties / type / description
      Previous value: -"Access entry type"New value: +"IAM principal type"
    • addedInput schema / properties / type / enum
      Added value: +[
+  "USER",
+  "ROLE"
+]
    • changedInput schema / required
      Previous value: -[
-  "clusterUuid"
-]New value: +[
+  "clusterUuid",
+  "type",
+  "entry"
+]
  2. First observedv1.10.1

TDQS

A4/5.0
Behavior3/5

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

Annotations only declare destructiveHint=false, so the description carries most of the behavioral burden. It usefully discloses the authType=API prerequisite, but says nothing about idempotency/duplicate-entry behavior, permissions required, or what happens if groups and policies are both omitted.

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?

One sentence describing the operation followed by a one-line prerequisite, with the core purpose front-loaded. No filler or redundant restatement of the tool name.

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 5-parameter mutation tool with no output schema, the description covers purpose, the mapping semantics, and a key prerequisite. It leaves minor gaps (duplicate/conflict handling, permission requirements), but nothing that would cause an agent to invoke it incorrectly.

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%, so every parameter (type, entry, groups, policies, clusterUuid) is already documented in the schema. The description restates the USER/ROLE-NRN and groups/policies concepts but adds no syntax, format, or constraint detail beyond the schema — the baseline 3 applies.

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?

States a specific verb (Create) and resource (IAM access entry for an NKS cluster), and goes further by explaining the semantic effect: mapping an IAM USER or ROLE (NRN) to Kubernetes groups and/or NKS access policies. This clearly distinguishes it from the sibling list/get/update/delete_access_entry tools without requiring the schema to be opened.

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?

Provides a real precondition — 'Requires authType=API' — which tells the agent the cluster must be configured a certain way before this call will work. It doesn't explicitly name alternatives or state when not to use it, but the create-vs-update/delete distinction is unambiguous from the name and purpose.

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