ncloud-mcp-server

ncloud_datastream_delete_connector

DestructiveIdempotent

Delete a Data Stream connector by providing topic and connector IDs. Set confirm=true to execute the destructive operation.

Instructions

⚠️ Destructive: Delete a Data Stream connector. 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": {
      "topicId": "<topicId>",
      "connectorId": "<connectorId>"
    },
    "name": "ncloud_datastream_delete_connector"
  }
}

Input Schema

Name	Required	Description
`confirm`	No	Must be true to execute the destructive operation
`topicId`	Yes	Topic ID
`connectorId`	Yes	Connector ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.10.1Jul 29, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already set destructiveHint=true and idempotentHint=true. The description adds context by explicitly warning 'Destructive' and requiring confirm=true, which reinforces the behavior and clarifies execution requirements.

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 extremely concise: a single sentence with a warning emoji, front-loading the destructive nature. No wasted words.

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 low complexity (simple delete, 3 params), the description is mostly complete. It covers the destructive behavior and confirmation requirement. However, it lacks details on post-deletion outcomes or prerequisites, which could enhance completeness.

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 coverage is 100%, so the schema already documents all parameters. The description only references the confirm parameter but does not add new meaning beyond the schema's description. Baseline of 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 the action ('Delete a Data Stream connector') and specifies the resource (connector). It distinguishes itself from sibling tools like create_connector and get_connector by explicitly mentioning deletion.

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 includes a warning emoji and states it is destructive, requiring confirm=true to execute. This provides clear guidance on when to use (i.e., with confirmation) but does not explicitly mention when not to use or provide alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server