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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_cdss_get_config_group_detail

Read-only

Retrieve CDSS config group details (name, Kafka version, description) by specifying config group number and Kafka version code.

Instructions

Get Config Group details (name, Kafka version, description) for a CDSS config group

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": {
      "configGroupNo": "<configGroupNo>",
      "kafkaVersionCode": "<kafkaVersionCode>"
    },
    "name": "ncloud_cdss_get_config_group_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
configGroupNoYesConfig group number (from ncloud_cdss_list_config_groups)
kafkaVersionCodeYesKafka version code of the group (from ncloud_cdss_get_kafka_versions)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.15.0
    • changedInput schema / properties / configGroupNo / description
      Previous value: -"Config group number"New value: +"Config group number (from ncloud_cdss_list_config_groups)"
    • addedInput schema / properties / kafkaVersionCode
      Added value: +{
+  "description": "Kafka version code of the group (from ncloud_cdss_get_kafka_versions)",
+  "type": "number"
+}
    • changedInput schema / required
      Previous value: -[
-  "configGroupNo"
-]New value: +[
+  "configGroupNo",
+  "kafkaVersionCode"
+]
  2. First observedv1.10.1

TDQS

B3.4/5.0
Behavior3/5

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

The description says 'Get' and the readOnlyHint=true annotation already establishes that this is a safe read operation, so there is no contradiction. It adds a little context by naming the returned detail fields, but it does not describe additional behavior such as error cases, response shape, or any side effects.

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 focused sentence with no filler or redundancy. The returned fields are front-loaded, and 'for a CDSS config group' adds the necessary domain context without bloat.

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?

With only two required parameters fully documented in the schema and readOnlyHint set, the agent has enough to call this tool correctly. There is no output schema, but the description compensates by naming the returned fields; it could be more complete by noting response format or error behavior.

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 coverage is 100%, and each parameter already has a description, including where its value comes from. The prose description does not add meaning beyond the schema's parameter documentation, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Get') and resource ('Config Group details'), and it enumerates the returned fields (name, Kafka version, description). It is clearly a detail-getter versus ncloud_cdss_list_config_groups, but it does not explicitly name or contrast any sibling.

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 gives no when-to-use, when-not-to-use, or alternative tool guidance. The input schema hints that parameter values come from ncloud_cdss_list_config_groups and ncloud_cdss_get_kafka_versions, but the description itself does not state sequencing 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