ncloud-gov-mcp-server

ncloud_delete_object

DestructiveIdempotent

Permanently delete an object from a Naver Cloud Object Storage bucket. Requires explicit confirmation to execute.

Instructions

⚠️ Destructive: Permanently delete an object from an Object Storage bucket. 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": {
      "bucketName": "<bucketName>",
      "key": "<key>"
    },
    "name": "ncloud_delete_object"
  }
}

Input Schema

Name	Required	Description
`key`	Yes	Object key (path) to delete
`confirm`	No	Must be true to actually execute the destructive operation
`bucketName`	Yes	Name of the bucket

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 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 the critical behavioral detail that deletion is permanent and requires explicit confirmation (confirm=true), which goes beyond the annotation flags by explaining the safety gate and irreversible nature.

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 a single, well-structured sentence with a warning emoji up front, followed by the action and execution requirement. Every word contributes value; no redundancy or filler.

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?

This is a simple delete operation with three well-documented parameters and no output schema. The description covers the purpose, permanence, and confirmation requirement, which is sufficient for an agent to select and safely invoke the tool.

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% with clear descriptions for all three parameters (bucketName, key, confirm). The description echoes the confirm parameter behavior but adds no new meaning beyond what the schema already provides. 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 tool's action: 'Permanently delete an object from an Object Storage bucket.' It specifies the verb (delete), the resource (object in a bucket), and the permanence, distinguishing it from sibling tools like ncloud_delete_multiple_objects and ncloud_delete_bucket.

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 clear operational context by warning 'Destructive' and instructing the agent to 'Set confirm=true to execute.' It implies the prerequisite that confirm must be true, but it does not explicitly mention when to use this tool over alternatives (e.g., ncloud_delete_multiple_objects).

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

Deploy Server