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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_kms_add_acl_rule

Add IPv4 addresses to a KMS key's IP ACL so token requests from those IPs are allowed. Whitelist addresses to grant access.

Instructions

Add IPv4 addresses to the IP ACL of a KMS key to allow token requests from those IPs.

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": {
      "keyTag": "<keyTag>",
      "ipList": "<ipList>"
    },
    "name": "ncloud_kms_add_acl_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipListYesIPv4 addresses to allow (e.g. ['192.168.1.1'])
keyTagYesKey tag - unique identifier derived from key name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.1
    • removedInput schema / properties / ip
      Removed value: -{
-  "description": "IP address to allow (e.g., '192.168.1.1' or CIDR '192.168.1.0/24')",
-  "type": "string"
-}
    • addedInput schema / properties / ipList
      Added value: +{
+  "description": "IPv4 addresses to allow (e.g. ['192.168.1.1'])",
+  "items": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array"
+}
    • removedInput schema / properties / memo
      Removed value: -{
-  "description": "Description for this ACL rule",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "keyTag",
-  "ip"
-]New value: +[
+  "keyTag",
+  "ipList"
+]
  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 only provide destructiveHint=false, so the description carries most of the behavioral burden. It adds useful effect context by stating that the added IPs will 'allow token requests from those IPs', but it does not disclose whether the operation appends to or replaces existing ACL entries, what permissions are required, or whether the ACL must already be active.

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 a single front-loaded sentence with no redundant or filler content. Every clause contributes to identifying the operation and its effect.

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?

For a simple two-parameter mutation tool with no output schema and sparse annotations, the description covers the core action and effect. However, it omits operationally relevant context such as whether the ACL must be enabled, whether the add is additive or replacing, and what the caller should expect afterward.

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%, with both keyTag and ipList documented directly in the schema. The description adds no further parameter-level meaning such as IP format constraints or key tag derivation, so the baseline of 3 applies.

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 (Add), resource (IPv4 addresses to the IP ACL of a KMS key), and effect (allow token requests from those IPs). It is clear enough to distinguish from the sibling delete_acl_rule by action, but it does not explicitly contrast itself with alternatives such as ncloud_kms_enable_ip_acl or ncloud_kms_get_acl_rule_list.

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 when-to-use or when-not-to-use guidance. It never mentions prerequisites (e.g., whether IP ACL must already be enabled) or points to alternatives like enable_ip_acl or delete_acl_rule. The effect statement implies a use case, but there is no explicit routing.

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