Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_ses_change_disk_size

Idempotent

Adjust Search Engine Service cluster disk capacity by providing the cluster instance number and a new larger disk size in 10GB increments.

Instructions

Change data node disk capacity for a Search Engine Service cluster

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
diskSizeYesNew storage size in GB (10GB increments; must be larger than the current size)
serviceGroupInstanceNoYesCluster instance number (sent in the body, as a number)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.15.0
    • removedInput schema / properties / dataNodeStorageSize
      Removed value: -{
-  "description": "New storage size in GB (100-2000, 10GB increment)",
-  "type": "number"
-}
    • addedInput schema / properties / diskSize
      Added value: +{
+  "description": "New storage size in GB (10GB increments; must be larger than the current size)",
+  "type": "number"
+}
    • changedInput schema / properties / serviceGroupInstanceNo / description
      Previous value: -"Cluster instance number"New value: +"Cluster instance number (sent in the body, as a number)"
    • changedInput schema / properties / serviceGroupInstanceNo / type
      Previous value: -"string"New value: +"number"
    • changedInput schema / required
      Previous value: -[
-  "serviceGroupInstanceNo",
-  "dataNodeStorageSize"
-]New value: +[
+  "serviceGroupInstanceNo",
+  "diskSize"
+]
  2. First observedv1.10.1

TDQS

A4/5.0
Behavior3/5

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

Annotations declare idempotentHint=true and destructiveHint=false, which already convey that the operation is safe and repeatable. The description adds no further behavioral context, such as whether the cluster must be stopped, if the operation is asynchronous, or if there is any downtime. It simply restates the tool's function without additional insight beyond the 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, front-loaded sentence with no filler. Every word contributes to the core purpose, making it highly efficient and easy to parse for an agent.

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 two-parameter tool with no output schema and annotations covering safety, the description is largely complete. It clearly states the action and target. The only minor gap is not explicitly distinguishing from sibling change tools, but the name and description make the purpose unambiguous.

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 input schema provides 100% coverage, with detailed descriptions for both parameters (diskSize with GB increments and must be larger than current; serviceGroupInstanceNo as a number). The description does not add any extra meaning beyond what the schema already states, so it meets the baseline without enhancing parameter understanding.

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 states a specific action: 'Change data node disk capacity for a Search Engine Service cluster'. It clearly identifies the verb (change), the resource (data node disk capacity), and the context (Search Engine Service cluster). This distinguishes it from sibling tools like ncloud_ses_change_node_spec which alters CPU/memory specs, not disk capacity.

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 implies its usage context (changing disk capacity for SES data nodes) but does not explicitly mention when to use it versus alternatives. It doesn't state exclusions or refer to sibling tools. However, the action is clear enough for an agent to infer it is the appropriate tool for disk resizing, as opposed to node spec changes.

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