Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_delete_cache_config_group

DestructiveIdempotent

Permanently delete a Cloud Cache config group when no instance is attached. Use confirm=true to execute; otherwise, the operation is prevented. Requires the config group number and region context.

Instructions

⚠️ Destructive: Permanently delete a Cloud Cache config group. A group still applied to an instance cannot be deleted — delete the instance first. Set confirm=true to execute.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoMust be true to actually execute the destructive operation
regionCodeNoRegion code (e.g., KR, JPN, SGN)
configGroupNoYesConfig group number to delete (from ncloud_list_cache_config_groups)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.15.0
    • removedInput schema / properties / cloudCacheConfigGroupNo
      Removed value: -{
-  "description": "Cloud Cache config group number to delete",
-  "type": "string"
-}
    • addedInput schema / properties / configGroupNo
      Added value: +{
+  "description": "Config group number to delete (from ncloud_list_cache_config_groups)",
+  "type": "string"
+}
    • addedInput schema / properties / regionCode
      Added value: +{
+  "description": "Region code (e.g., KR, JPN, SGN)",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "cloudCacheConfigGroupNo"
-]New value: +[
+  "configGroupNo"
+]
  2. First observedv1.10.1

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the destructiveHint=true and idempotentHint=true annotations, the description adds meaningful behavioral context: deletion is permanent, there is a dependency that prevents deletion if the group is in use, and the confirm flag is a required safety switch. This gives the agent a clear mental model of the operation's consequences and prerequisites.

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?

Two sentences, with the danger warning front-loaded and the critical precondition and execution flag stated efficiently. Every sentence earns its place; there is no fluff or redundancy.

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 delete operation with 3 parameters and no output schema, the description covers the essential points: what is deleted, that it is permanent, the condition blocking deletion, and the required confirm flag. It could theoretically mention what the API returns or how to verify success, but that is not necessary for a correctly formed call, so this is nearly complete.

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%, so each parameter (confirm, regionCode, configGroupNo) already has a meaningful description. The tool description does not add new parameter semantics beyond restating that confirm=true is required, which is already present in the schema. Thus the baseline 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 states a specific verb ('delete') and resource ('Cloud Cache config group') with an explicit permanence qualifier ('Permanently delete'). This clearly distinguishes it from sibling delete tools that target different resource types such as ncloud_delete_cache_instance or ncloud_delete_bucket.

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 provides concrete guardrails: it tells the agent that a group still applied to an instance cannot be deleted defining a when-not situation, and instructs to delete the instance first as a prerequisite. It also requires confirm=true to execute, which is operational guidance. The only minor gap is that it does not explicitly name an alternative tool, though the action 'delete the instance first' implicitly points to ncloud_delete_cache_instance.

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