Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_nks_set_ip_acl

Idempotent

Configure IP ACL rules for an NKS cluster to restrict API server access, specifying allow or deny entries and a default action for unmatched addresses.

Instructions

Configure IP ACL for an NKS cluster to restrict API server access. defaultAction (allow|deny) is required and applies to addresses not matched by entries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entriesNoIP ACL entries (optional)
clusterUuidYesUUID of the cluster
defaultActionYesDefault action for addresses not matched by any entry

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2.0.1
    • addedInput schema / properties / defaultAction
      Added value: +{
+  "description": "Default action for addresses not matched by any entry",
+  "enum": [
+    "allow",
+    "deny"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / entries / description
      Previous value: -"IP ACL entries"New value: +"IP ACL entries (optional)"
    • changedInput schema / properties / entries / items / properties / action / description
      Previous value: -"ACL action (allow or deny)"New value: +"ACL action for this entry"
    • addedInput schema / properties / entries / items / properties / action / enum
      Added value: +[
+  "allow",
+  "deny"
+]
    • addedInput schema / properties / entries / items / properties / comment
      Added value: +{
+  "description": "Free-text comment",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "clusterUuid",
-  "entries"
-]New value: +[
+  "clusterUuid",
+  "defaultAction"
+]
  2. First observedv1.10.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations declare idempotentHint=true and destructiveHint=false, so the safety profile is partly covered. The description adds that defaultAction is required and applies to unmatched addresses, but it does not disclose whether existing ACL entries are replaced or merged, nor authentication requirements. This is additional context, but incomplete for a mutation/config tool.

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?

Two tightly written sentences. The core purpose is front-loaded, and the required defaultAction behavior is stated without filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is minimally adequate for a config tool whose schema is fully documented and annotations cover idempotency/non-destructiveness. However, it omits key behavioral context such as whether the provided entries replace or augment existing ACL rules, which an agent would need to invoke correctly.

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 the schema already documents all three parameters in detail. The description restates the defaultAction behavior that the schema also describes, but adds no meaningful syntax, constraints, or format details beyond structured data.

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 states a specific verb (Configure) and resource (IP ACL for an NKS cluster), plus the security goal of restricting API server access. It is clear, but does not explicitly differentiate from sibling tools such as ncloud_nks_get_ip_acl, 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no explicit guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. It implies usage by stating the tool configures an IP ACL, but an agent gets no routing help among the many NKS and ACL-related siblings.

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