Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_kms_delete_acl_rule

DestructiveIdempotent

Removes IPv4 addresses from a KMS key's IP ACL to revoke access for those addresses. This destructive action requires confirm=true to execute.

Instructions

⚠️ Destructive: Remove IPv4 addresses from the IP ACL of a KMS key. Set confirm=true to execute.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipListYesIPv4 addresses to remove from the ACL (required)
keyTagYesKey tag - unique identifier derived from key name (required)
confirmNoMust be true to actually execute the destructive operation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.1
    • addedInput schema / properties / ipList
      Added value: +{
+  "description": "IPv4 addresses to remove from the ACL (required)",
+  "items": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array"
+}
    • removedInput schema / properties / ruleId
      Removed value: -{
-  "description": "ACL rule ID to delete (required)",
-  "minLength": 1,
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "keyTag",
-  "ruleId"
-]New value: +[
+  "keyTag",
+  "ipList"
+]
  2. First observedv1.10.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the schema documents the confirm gate, so the description's ⚠️ warning and confirm note largely restate structured data. It adds the IPv4 scoping detail, but does not describe blast radius or auth requirements beyond what is already covered.

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 sentences with zero waste. The destructive warning and the execution gate are front-loaded, so the most important fact reaches the agent first.

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?

No output schema exists, but for a destructive list-removal tool the description covers purpose and the confirm gate adequately; the safety profile is carried by annotations and the parameter detail by the schema. It stops just short of stating preconditions (e.g. ACL must already exist).

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 baseline is 3. The description echoes the confirm=true execution gate but adds no syntax, format, or constraint meaning beyond what the schema already provides for keyTag, ipList, and confirm.

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 and resource: 'Remove IPv4 addresses from the IP ACL of a KMS key.' The verb 'Remove' cleanly distinguishes it from siblings like ncloud_kms_add_acl_rule and ncloud_kms_get_acl_rule_list, so an agent can tell what it does without opening the schema.

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?

Usage is only implied: it's implicitly for removing ACL entries and it flags the confirm=true requirement. There is no explicit when-to-use framing, no mention of prerequisites or of sibling alternatives (enable/disable IP ACL), leaving the agent to infer the appropriate context.

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