ncloud-mcp-server

ncloud_edge_delete_profile

DestructiveIdempotent

Delete a Global Edge CDN profile permanently. Ensure all edges under the profile are deleted first, then set confirm=true to execute this destructive operation.

Instructions

⚠️ Destructive: Permanently delete a Global Edge CDN profile. All edges under this profile must be deleted first. 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": {
      "profileId": "<profileId>"
    },
    "name": "ncloud_edge_delete_profile"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No	Must be true to actually execute the destructive operation
`profileId`	Yes	Profile ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.10.1Jul 29, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds value by explicitly stating the destructive nature with a warning symbol, the precondition about edges, and the requirement for a confirm flag. This additional context shows the tool's behavior beyond what annotations provide.

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: two sentences with no wasted words. It front-loads the destructive nature with a warning emoji, then states the action and prerequisites. Every sentence serves a purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 2 parameters (both documented), no output schema, and annotations present, the description is complete. It covers the purpose, prerequisites, and execution requirement (confirm). No additional information seems necessary for the agent to use this 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?

Schema coverage is 100%, so the schema documents both parameters (profileId and confirm). The description mentions the confirm parameter requirement, but this largely repeats the schema's description. Baseline 3 is appropriate because the description adds minimal additional meaning 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 clearly states the tool's purpose: permanently delete a Global Edge CDN profile. It specifies the resource (profile) and action (delete), and distinguishes from sibling tools like ncloud_edge_delete_edge which are for edges, not profiles.

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 a clear prerequisite: all edges under the profile must be deleted first. It also instructs the agent to set confirm=true to execute. However, it does not explicitly state when not to use this tool or mention alternatives, which would make it a 5.

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

Deploy Server