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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_cdss_get_cluster_detail

Read-only

Retrieve detailed configuration and status for a specific CDSS Kafka cluster using its cluster instance number.

Instructions

Get detailed information about a specific CDSS (Kafka) cluster

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_get_cluster_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceGroupInstanceNoYesCluster instance number from cluster list

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description's 'Get detailed information' aligns with a read-only operation. The description adds no additional behavioral context beyond the annotation, such as response format or data scope, but no contradiction exists.

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 concise sentence fully states the tool's purpose with no wasted words. It is appropriately front-loaded and easy to parse.

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?

Given the simple structure (one parameter, read-only annotation, no output schema), the description is sufficiently complete. It does not enumerate what 'detailed information' includes, but this is acceptable given the lack of output schema and the straightforward nature of a get-detail operation.

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?

The parameter schema has 100% coverage with a clear description ('Cluster instance number from cluster list'). The main description reinforces the parameter's meaning by calling out 'specific cluster'. This adds value beyond the schema by indicating the source of the identifier.

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 uses a specific verb ('Get') and resource ('CDSS (Kafka) cluster'), clearly indicating this tool fetches details for one specific cluster. It distinguishes itself from siblings like ncloud_cdss_list_clusters (list) and ncloud_cdss_get_cluster_status (status) by focusing on detailed information.

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

Usage Guidelines4/5

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

The phrase 'specific CDSS (Kafka) cluster' implies use when you need details of a particular cluster rather than a list or status. However, it does not explicitly name alternative tools like get_cluster_status or list_clusters, so exclusions are not stated.

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