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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_kms_get_acl_rule_list

Read-only

Retrieve the IP addresses allowed by a KMS key's IP ACL using its key tag.

Instructions

Get the list of IP addresses allowed by the IP ACL of a KMS key.

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>"
    },
    "name": "ncloud_kms_get_acl_rule_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyTagYesKey tag - unique identifier derived from key name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safe-read nature is covered. The description adds that the result is the list of allowed IP addresses, which is useful, but says nothing about ordering, pagination, or behavior when no ACL is configured.

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, front-loaded with the verb and the returned resource, with zero filler.

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 single-parameter read tool with annotations covering the safety profile and no output schema, stating that it returns the ACL-allowed IP list is nearly sufficient. Slightly light on whether an empty/no-ACL state is possible.

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% and the lone keyTag parameter is documented in the schema, so the description need not carry it. It adds no extra meaning about the identifier beyond the schema.

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 (Get), resource (ACL rule list / allowed IP addresses), and scope (of a KMS key's IP ACL). It is easily distinguishable from siblings like ncloud_kms_add_acl_rule or ncloud_kms_delete_acl_rule.

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?

No indication of when to call this versus alternatives such as ncloud_kms_enable_ip_acl, ncloud_kms_disable_ip_acl, or the add/delete ACL rule tools. No prerequisites (e.g. that the key must exist or that IP ACL must be enabled) are mentioned.

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