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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_cdss_restart_cmak

Idempotent

Restart CMAK (Cluster Manager for Apache Kafka) in a CDSS cluster by specifying the cluster instance number. Use this action to recover or apply configuration changes.

Instructions

Restart CMAK (Cluster Manager for Apache Kafka) in a CDSS 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_restart_cmak"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceGroupInstanceNoYesCluster instance number

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?

Annotations already disclose idempotency and non-destructiveness. The description adds only the target component and cluster context, but does not discuss potential side effects like temporary unavailability of the CMAK UI or that only CMAK is restarted, not Kafka brokers. With annotations covering the safety profile, this is a minimal passing score.

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 sentence of 14 words, front-loaded with the verb and resource. It contains no fluff or repetition, and every word contributes to understanding what the tool does.

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 tool with one parameter and no output schema, the description is adequate. It specifies the operation, resource, and cluster context. Minor gaps like potential downtime or prerequisites are not critical given the annotations cover safety, and the description is otherwise sufficient.

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 description coverage is 100%, with the sole parameter 'serviceGroupInstanceNo' already described as 'Cluster instance number'. The description adds no extra parameter details beyond that, so the baseline score of 3 applies.

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 ('Restart') and resource ('CMAK (Cluster Manager for Apache Kafka)') with a clear scope ('in a CDSS cluster'). It distinguishes from sibling tools like ncloud_cdss_restart_kafka and ncloud_cdss_restart_all_services by targeting the CMAK component specifically.

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 description clearly identifies the tool's purpose, making the usage context obvious. However, it does not explicitly state when not to use this tool or mention alternatives (e.g., use restart_kafka for Kafka brokers). The sibling list provides context but the description itself lacks direct comparative guidance.

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