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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_cdss_disable_public_endpoint

Idempotent

Disable public endpoint for broker nodes to secure your cluster by preventing external access.

Instructions

Disable 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_disable_public_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceGroupInstanceNoYesCluster instance number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the safety profile is known. The description adds the scope 'broker nodes' but does not disclose side effects (e.g., making broker nodes inaccessible from public networks) or any state change implications beyond the basic action. No contradiction with annotations.

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, direct sentence with no unnecessary words. It is front-loaded with the action and clearly scoped, making it easy to parse.

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?

With one parameter and no output schema, the description is simple but lacks context about when to use it, related enable/disable tools, and potential impact. The sibling CDSS tools and the presence of an enable_public_endpoint counterpart suggest more contextual information could be provided.

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 fully describes the sole parameter (serviceGroupInstanceNo) as 'Cluster instance number' with 100% coverage. The description does not add additional meaning about how to obtain or use the instance number, so it does not improve on the schema.

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 ('Disable') and the target resource ('public endpoint') with a specific scope ('for broker nodes'). It distinguishes from sibling tools like ncloud_cdss_enable_public_endpoint and ncloud_cdss_disable_public_domain by naming the exact operation.

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 only a single statement of the action with no guidance on when to use it, prerequisites, or alternatives. It does not mention the inverse relationship with enable_public_endpoint or any conditions under which this should be invoked.

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