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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_nks_list_worker_nodes

Read-only

List worker nodes in an NKS cluster by providing its UUID to view node details for cluster management.

Instructions

List worker nodes in 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_worker_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
clusterUuidYesUUID of the cluster

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?

The readOnlyHint annotation already declares this as a read-only operation. The description adds minimal behavior beyond that—it identifies the resource scope ('in an NKS cluster') but doesn't disclose any additional traits like pagination, filtering, or required cluster UUID context.

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 concise sentence with clear structure, containing no unnecessary words or fluff.

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 simple list tool with one required parameter, read-only annotation, and no output schema, the description adequately conveys the core function. It lacks any mention of return content or edge cases but remains sufficient for basic selection and invocation.

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% for the single clusterUuid parameter ('UUID of the cluster'). The description adds no further semantic meaning beyond the schema, which is sufficient for a one-parameter tool, hence baseline 3.

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 clearly states the verb 'List' and the resource 'worker nodes in an NKS cluster', differentiating it from sibling tools like ncloud_nks_list_node_pools which operate on a different resource (node pools).

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 provides no guidance on when to use this tool versus alternatives such as ncloud_nks_list_node_pools or ncloud_nks_get_cluster. Usage context is only implied by the simple 'list' verb, with no exclusions or alternatives 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