ncloud-gov-mcp-server

ncloud_abort_multipart_upload

Destructive

Abort an in-progress multipart upload and delete its uploaded parts. Requires explicit confirmation to execute, preventing accidental data loss.

Instructions

⚠️ Destructive: Abort a multipart upload and delete all uploaded parts. 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>",
      "objectName": "<objectName>",
      "uploadId": "<uploadId>"
    },
    "name": "ncloud_abort_multipart_upload"
  }
}

Input Schema

Name	Required	Description
`confirm`	No	Must be true to actually execute the destructive operation
`uploadId`	Yes	Upload ID of the multipart upload to abort
`bucketName`	Yes	Name of the bucket
`objectName`	Yes	Object key (path) for the multipart upload

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4.2/5.0

Behavior5/5

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

The description goes beyond the destructiveHint annotation by explicitly warning '⚠️ Destructive' and detailing what gets destroyed ('delete all uploaded parts'). It also introduces the safety requirement 'Set confirm=true to execute', which is critical behavioral context not present in the annotation alone.

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, high-impact sentence that front-loads the destructive warning and clearly states the action and confirm requirement. No filler or redundant information; every word earns its place.

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 destructive action with 4 well-documented parameters and no output schema, the description covers the essential purpose, destructive effect, and confirmation gate. It lacks explicit references to related tools for obtaining uploadId, but this is not critical given the schema and name. Slight gap in usage context prevents a 5.

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%, so parameters are already well-documented. The description reinforces the confirm parameter's necessity but does not add new meaning beyond the schema's existing descriptions for bucketName, objectName, uploadId, or confirm. 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 the action: 'Abort a multipart upload and delete all uploaded parts.' This specifies the verb (abort), resource (multipart upload), and the effect (delete parts), distinguishing it from sibling operations like complete_multipart_upload or upload_part.

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 implies usage for cancelling an in-progress multipart upload, but does not explicitly contrast with alternatives (e.g., complete_multipart_upload) or provide when-to-use/when-not-to-use guidance. The name and warning make the primary use case clear, but no exclusions or alternatives are mentioned.

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

Deploy Server