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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_delete_mysql_instance

DestructiveIdempotent

Permanently delete a Cloud DB for MySQL instance. Requires confirm=true to process the deletion.

Instructions

⚠️ Destructive: Permanently delete a Cloud DB for MySQL instance. Set confirm=true to execute.

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": {
      "cloudMysqlInstanceNo": "<cloudMysqlInstanceNo>"
    },
    "name": "ncloud_delete_mysql_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to actually execute the destructive operation
cloudMysqlInstanceNoYesCloud MySQL instance number to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructive and idempotent, but the description adds that deletion is permanent and requires confirm=true, clarifying the actual execution gate and irreversibility beyond the annotation flags.

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?

Single concise sentence with a clear warning symbol, front-loading the destructive nature and execution requirement. Every word earns its place.

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 delete tool with comprehensive schema and annotations, the description covers the essential information: what is deleted, permanence, and the confirm gate. It does not need to explain return values due to lack of output schema.

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 covers 100% of parameters, so baseline is 3. The description reinforces the confirm parameter's purpose but adds no new semantic information about cloudMysqlInstanceNo beyond the schema.

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 'Permanently delete a Cloud DB for MySQL instance' with a specific verb and resource, clearly distinguishing it from sibling tools like ncloud_delete_mysql_server or ncloud_delete_mysql_databases.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives. It only warns about destructiveness and the confirm parameter; no mention of when to choose this over ncloud_delete_mysql_server or other delete operations.

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