Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_cdss_get_kafka_config

Read-only

Retrieve Kafka configuration settings for a config group, showing default and custom values per setting. Provide the config group number and Kafka version code to get the full configuration.

Instructions

Get the Kafka settings held by a Config Group (default and custom values per setting)

Input Schema

TableJSON 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

A3.8/5.0
Behavior4/5

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

The description discloses that the tool returns both default and custom values per setting, which is behavioral context beyond the readOnlyHint annotation. It adds value by explaining what the response contains, even though it does not detail the exact response structure. 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, concise sentence that directly states the purpose and includes a useful detail about default and custom values. No redundant or unnecessary words, and it is front-loaded with the core action.

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 read operation with two well-documented parameters and readOnlyHint annotation, the description is mostly complete. It mentions the key aspect of returning default and custom values, which gives the agent an idea of the output, even without an output schema. Slight gap: it doesn't specify what 'settings' are, but this is minor for a config retrieval tool.

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 already provides 100% coverage for both parameters with descriptions that reference other tools for sourcing values. The description adds no additional parameter-specific semantics, so it does not exceed the baseline for high schema coverage.

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 clearly states the tool retrieves Kafka settings from a Config Group, using a specific verb and resource. It mentions the return includes default and custom values, but does not explicitly differentiate from sibling tools like ncloud_cdss_get_config_group_detail, so it lacks explicit sibling differentiation.

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 usage by mentioning 'held by a Config Group', which suggests it is for retrieving settings of a specific group. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention any exclusions or conditions. Guidance is implied rather than explicit.

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