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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_nks_get_oidc

Read-only

Retrieve OIDC provider settings for a specified NKS cluster by UUID to configure Kubernetes authentication and identity federation.

Instructions

Get OIDC (OpenID Connect) provider configuration 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_get_oidc"
  }
}

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 indicates this is a safe read operation, and the description's 'Get' is consistent with that. The description adds no further behavioral context (e.g., whether the cluster must exist, error scenarios, or what specifically is returned), but it does not contradict the annotation either.

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 no redundant words. It front-loads the action and resource, and there is no filler or unnecessary detail.

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?

Given the tool's simplicity (one required parameter, no nested objects, no output schema) and the clear purpose, the description is largely complete. However, it does not describe the return value structure (e.g., what an OIDC configuration contains), which could be useful given there is no output schema.

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%; the single parameter 'clusterUuid' is described as 'UUID of the cluster', which is adequate. The description does not add any extra parameter semantics beyond this, so the baseline 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 clearly states the action ('Get') and the resource ('OIDC provider configuration for an NKS cluster'), and it distinguishes the tool from siblings like ncloud_nks_set_oidc by specifying a read operation. The naming and description are unambiguous.

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 usage guidance is provided beyond the action itself. The description does not mention when to use this tool versus ncloud_nks_set_oidc (for configuring OIDC) or ncloud_nks_get_cluster (for general cluster info), nor does it specify any prerequisites or alternatives.

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