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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_delete_integration

DestructiveIdempotent

Delete a Cloud Insight integration by providing its ID and confirming the operation. This destructive action requires confirmation to proceed.

Instructions

⚠️ Destructive: Delete a Cloud Insight integration. 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": {
      "integrationId": "<integrationId>"
    },
    "name": "ncloud_delete_integration"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to actually execute the destructive operation
integrationIdYesIntegration ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already provide destructiveHint and idempotentHint, and the description adds the specific resource type and the critical behavioral detail that confirm=true is required to execute. It does not contradict the idempotent hint and offers meaningful context beyond the structured 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 short sentences, with the destructive warning front-loaded and the key confirmation instruction included. Every word contributes to understanding the tool's purpose and usage.

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 two parameters, the description covers the destructive nature, the specific resource, and the confirmation requirement. Annotations cover idempotency and destructiveness, and no output schema requires return-value explanation. Minor gap: it doesn't explicitly state permanence or post-delete effects, but the destructive warning sufficiently implies them.

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 both parameters clearly described in the schema. The tool description merely repeats the confirm=true requirement already present in the schema, adding no new parameter semantics. Baseline 3 is appropriate.

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 a specific verb 'Delete' and resource 'Cloud Insight integration', distinguishing it from sibling create, update, get, and list operations. The destructive warning reinforces the tool's purpose without ambiguity.

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

Usage Guidelines3/5

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

The description provides a clear prerequisite (confirm=true) and warns of destructive behavior, but it does not explicitly state when to use this tool versus alternatives like ncloud_get_integration or ncloud_list_integrations. Usage is implied rather than explicitly contrasted with read or update tools.

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