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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_cdss_get_node_products

Read-only

Retrieve available node server types (product codes) needed to create a CDSS cluster.

Instructions

Get available node server types (product codes) for CDSS cluster creation

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ncloud_cdss_get_node_products"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4/5.0
Behavior3/5

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

The description is consistent with the readOnlyHint annotation, describing a 'get' operation. It adds purpose context (CDSS cluster creation) but does not disclose behavioral details such as whether the full list is returned, regional constraints, or output structure. The annotation provides the safety profile.

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?

One sentence, front-loaded with the verb 'Get', and zero filler. All words contribute to understanding the tool's purpose.

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 zero-parameter read-only lookup, the description is adequate. It states what is returned and the context. It could explicitly mention that it returns a list, but the simplicity of the tool and the presence of annotations make this a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero parameters, the schema is trivially covered. The description adds semantic value by explaining that the result is node server types (product codes), which is useful since there are no parameters to describe.

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 tool gets available node server types (product codes) for CDSS cluster creation. It uses a specific verb ('Get') and resource ('node server types (product codes)'), and the context ('for CDSS cluster creation') distinguishes it from sibling tools that list server specs, generations, or images.

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

Usage Guidelines3/5

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

The description implies this is used when selecting node server types for CDSS cluster creation, but it does not explicitly state when to use this tool versus alternatives like ncloud_cdss_get_server_spec_list or ncloud_cdss_get_server_generations. No exclusions or alternative guidance is provided.

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