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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_nks_list_access_entries

Read-only

List IAM access entries for an NKS cluster to audit Kubernetes permissions and manage access control. Requires authType=API on the cluster.

Instructions

List IAM access entries of an NKS cluster (requires authType=API on the 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

NameRequiredDescriptionDefault
clusterUuidYesUUID of the cluster

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnlyHint=true, so the safety profile is covered. The description contributes the authType=API cluster precondition, which is useful context beyond the annotations, but it says nothing about permissions, pagination, or result volume.

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?

A single front-loaded sentence that names the action first and appends the precondition in parentheses. No redundant or filler text.

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 one-parameter read tool with full schema coverage and no output schema, purpose plus precondition is close to complete. Return shape and pagination behavior are not addressed, but the essential call information is present.

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 single clusterUuid parameter is already documented in the schema. The description adds no syntax, format, or sourcing detail beyond what the schema provides, so baseline 3 is correct.

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?

States a specific verb (List) and resource (IAM access entries of an NKS cluster), which clearly separates it from the single-entry sibling ncloud_nks_get_access_entry and the mutating create/update/delete siblings. It stops short of explicitly naming those siblings, so it lands at a clear-but-not-differentiated 4.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The parenthetical "requires authType=API on the cluster" gives a concrete precondition the agent must check before calling, which is genuine usage context. It does not name an alternative tool or a when-not condition, so it is not a full 5.

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