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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_delete_launch_config

DestructiveIdempotent

Delete a launch configuration permanently. Set confirm=true to execute the destructive operation.

Instructions

⚠️ Destructive: Permanently delete a launch configuration. 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": {
      "launchConfigurationNo": "<launchConfigurationNo>"
    },
    "name": "ncloud_delete_launch_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to actually execute the destructive operation
launchConfigurationNoYesLaunch configuration 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?

The description adds value beyond the destructiveHint annotation by specifying the deletion is 'permanently' and by disclosing the confirmation mechanism ('Set confirm=true to execute'). This informs the agent that the operation is irreversible and requires an explicit opt-in, which is not captured by the annotations alone. No contradiction with 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 only two sentences, front-loaded with a clear destructive warning. '⚠️ Destructive: Permanently delete a launch configuration. Set confirm=true to execute.' Each sentence serves a distinct purpose and there is no redundant or verbose content.

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 delete operation, the destructive annotations, and fully documented parameters, the description covers the essential safety and execution context. It might have mentioned side effects (e.g., impact on related resources) or return values, but given the 100% schema coverage and clear annotations, it is sufficiently complete for an agent to invoke the tool correctly.

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 already provides full descriptions for both parameters: confirm ('Must be true to actually execute the destructive operation') and launchConfigurationNo ('Launch configuration number to delete'). The description's mention of 'Set confirm=true to execute' reiterates what the schema already explains. No additional parameter semantics are provided beyond the schema's 100% coverage.

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 clearly states the action: 'Permanently delete a launch configuration.' The verb 'delete' and the specific resource 'launch configuration' precisely identify the tool's function, distinguishing it from sibling tools like ncloud_list_launch_configs and ncloud_create_launch_config. The 'permanently' keyword adds an important qualifier.

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?

The description does not provide any context on when to use this tool versus alternatives. It does not mention related operations like listing or creating launch configurations, nor does it state prerequisites or exclusions. The only guidance is the confirm requirement, which is more about execution than usage context.

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