Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_ncs_delete_object

DestructiveIdempotent

Delete a Ncloud Storage object. Specify versionId to permanently remove a specific version; omit to add a delete marker. Set confirm and bypassGovernanceRetention to handle governance-locked objects.

Instructions

[Ncloud Storage] ⚠️ Destructive: Delete an object from a Ncloud Storage bucket (DELETE /{key}). In a versioning-enabled bucket, omitting versionId only adds a delete marker (the versions stay and keep billing); pass versionId to permanently remove one version. bypassGovernanceRetention=true is needed for objects under GOVERNANCE retention. Set confirm=true to execute.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesObject key (path) to delete
confirmNoMust be true to actually execute the destructive operation
versionIdNoVersion ID to delete permanently. Omit to delete the current version (adds a delete marker on versioned buckets)
bucketNameYesName of the Ncloud Storage bucket
bypassGovernanceRetentionNoSend x-amz-bypass-governance-retention: true to delete an object locked in GOVERNANCE mode (requires the bypass permission)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.15.0
    • changedInput schema / properties / bucketName / description
      Previous value: -"Name of the bucket"New value: +"Name of the Ncloud Storage bucket"
    • addedInput schema / properties / bypassGovernanceRetention
      Added value: +{
+  "default": false,
+  "description": "Send x-amz-bypass-governance-retention: true to delete an object locked in GOVERNANCE mode (requires the bypass permission)",
+  "type": "boolean"
+}
    • addedInput schema / properties / versionId
      Added value: +{
+  "description": "Version ID to delete permanently. Omit to delete the current version (adds a delete marker on versioned buckets)",
+  "type": "string"
+}
  2. First observedv1.10.1

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark destructiveHint=true, but the description adds critical behavioral details: the delete-marker behavior in versioned buckets, billing implications, the requirement for bypassGovernanceRetention under GOVERNANCE, and the confirm=true gate. This goes well beyond the annotation and fully discloses consequences of invocation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded with the destructive warning, then explains versioning, governance, and confirmation in sequence. Each sentence contributes meaningful information without redundancy, though it is slightly dense with technical details.

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 destructive delete operation, the description covers the essential execution requirements (confirm), versioning nuances, and retention bypass. It does not mention error cases or output format, but since there is no output schema and the tool is a straightforward delete, this is adequate. It lacks explicit guidance on prerequisites like bucket existence or permissions, but those are implicit in the operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 adds contextual meaning for versionId and bypassGovernanceRetention, explaining the versioning and retention scenarios that the schema descriptions only hint at. This extra explanation is useful for correct invocation.

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 deletes a single object from a Ncloud Storage bucket, including the HTTP method. It distinguishes from the plural sibling ncloud_ncs_delete_objects by the singular 'an object' and by explaining the versioning implications, making the tool's specific purpose unambiguous.

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 guidance on when to use versionId (to permanently remove a version vs. adding a delete marker) and when bypassGovernanceRetention is needed for GOVERNANCE-locked objects. However, it does not explicitly contrast with alternative delete tools (e.g., ncloud_ncs_delete_objects) beyond the singular/plural distinction.

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