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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_cdss_enable_public_endpoint

Idempotent

Enable a public endpoint for broker nodes in your cluster. Supply the cluster instance number to activate external access.

Instructions

Enable public endpoint for broker nodes

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": {
      "serviceGroupInstanceNo": "<serviceGroupInstanceNo>"
    },
    "name": "ncloud_cdss_enable_public_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceGroupInstanceNoYesCluster instance number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.3/5.0
Behavior2/5

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

The annotations already declare idempotentHint=true and destructiveHint=false, and the description does not add any additional behavioral context such as side effects, required permissions, or network implications. It only repeats the action from the name.

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 filler, front-loading the key verb and resource. Every word contributes to meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter enabling operation with annotations, the description is adequate but lacks context on prerequisites, what 'public endpoint' means in this CDSS context, or any expected effects on broker nodes. It is not misleading but leaves room for interpretation.

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 input schema covers 100% of parameters with a single required 'serviceGroupInstanceNo' described as 'Cluster instance number'. The description does not mention parameters, but with full schema coverage 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 'Enable public endpoint for broker nodes' uses a specific verb (Enable) and resource (public endpoint) with a clear scope (broker nodes). It distinguishes itself from siblings like ncloud_cdss_disable_public_endpoint and ncloud_cdss_enable_public_domain by clearly indicating the action and target.

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 only states the action; it does not provide when-to-use or when-not-to-use guidance, nor does it mention alternatives such as enabling a public domain or disabling the endpoint. No exclusions or prerequisites are noted.

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