Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_nks_update_access_entry

Idempotent

Update Kubernetes groups and NKS access policies for an IAM access entry, replacing existing lists with new ones.

Instructions

Update the Kubernetes groups and/or NKS access policies of an IAM access entry (PUT — the supplied lists replace the existing ones)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupsNoKubernetes group names (replaces the existing list)
policiesNoNKS access policies (replaces the existing list)
entryUuidYesIAM access entry UUID
clusterUuidYesUUID of the cluster

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2.0.1
    • removedInput schema / properties / accessEntryNo
      Removed value: -{
-  "description": "Access entry number",
-  "type": "number"
-}
    • addedInput schema / properties / entryUuid
      Added value: +{
+  "description": "IAM access entry UUID",
+  "type": "string"
+}
    • addedInput schema / properties / groups
      Added value: +{
+  "description": "Kubernetes group names (replaces the existing list)",
+  "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 (replaces the existing list)",
+  "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"
+}
    • changedInput schema / required
      Previous value: -[
-  "clusterUuid",
-  "accessEntryNo"
-]New value: +[
+  "clusterUuid",
+  "entryUuid"
+]
  2. First observedv1.10.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already disclose idempotency and non-destructiveness, and the description adds the important behavioral detail that supplied groups and policies replace existing lists. It does not cover auth requirements, rate limits, or what happens when a field is omitted, but the replacement semantics are a meaningful addition.

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 definition is a single front-loaded sentence with no wasted words. The essential operation and replacement behavior are conveyed immediately.

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?

Given the rich schema, annotations, and a 4-parameter update tool, the description is mostly sufficient: it states the updated fields and replacement semantics. It could more explicitly note that at least one of groups or policies must be supplied, and no output schema exists to cover return behavior.

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 all four parameters are already documented. The description mentions groups and policies but adds no syntax, format, or constraint information beyond what the schema and its field descriptions provide.

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?

The description names a specific verb (Update), resource (IAM access entry), and the fields affected (Kubernetes groups and NKS access policies). It does not explicitly name or differentiate from sibling tools such as create_access_entry or delete_access_entry, so it falls short of a 5.

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 PUT note and 'and/or' wording give implied usage context, but the description never states when to use this tool versus siblings or any prerequisites. It provides no explicit alternatives or exclusions.

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