ncloud-gov-mcp-server

ncloud_nks_list_access_entries

Read-only

List IAM access entries for an NKS cluster to review permissions and manage access control.

Instructions

List IAM access entries for an NKS cluster

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": {
      "clusterUuid": "<clusterUuid>"
    },
    "name": "ncloud_nks_list_access_entries"
  }
}

Input Schema

Name	Required	Description	Default
`clusterUuid`	Yes	UUID of the cluster

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.6/5.0

Behavior2/5

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

The readOnlyHint annotation already discloses the safe read-only nature of the tool. The description adds no behavioral context beyond that, such as pagination, required permissions, or response format.

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 filler or redundant details. It is appropriately concise for a simple list operation.

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?

This is a very simple tool with one well-documented parameter and a readOnly annotation. The description is sufficient for selecting and invoking the tool, though it omits any mention of the return list structure. Given the minimal complexity, this is adequate.

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?

The schema provides 100% coverage for the single clusterUuid parameter with the description 'UUID of the cluster'. The tool description does not add meaning beyond reinforcing that the list is for an NKS cluster, so the baseline of 3 applies.

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?

The description uses a specific verb ('List'), a clear resource ('IAM access entries'), and a scope ('for an NKS cluster'). It distinguishes well from sibling tools like ncloud_nks_create_access_entry, ncloud_nks_update_access_entry, ncloud_nks_delete_access_entry, and especially ncloud_nks_get_access_entry.

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 implied through the verb 'List' and the tool name, but there is no explicit guidance about when to choose this over ncloud_nks_get_access_entry or the mutation tools. No alternatives, exclusions, or preconditions 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