ncloud-gov-mcp-server

ncloud_copy_object

Copy an object within the same bucket or across buckets in Object Storage to duplicate data or reorganize storage.

Instructions

Copy an object within the same bucket or between different buckets in Object Storage

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>",
      "copySource": "<copySource>"
    },
    "name": "ncloud_copy_object"
  }
}

Input Schema

Name	Required	Description
`bucketName`	Yes	Destination bucket name
`copySource`	Yes	Source object in the format /{sourceBucket}/{sourceKey}
`objectName`	Yes	Destination object key (path)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

B3.2/5.0

Behavior2/5

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

Annotations are empty, so the description must disclose side effects. It states the copy action but omits overwrite semantics, server-side vs client-side behavior, metadata preservation, and permissions required. The description carries the full behavioral disclosure burden and fails to cover these critical traits.

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?

A single, front-loaded sentence with no fluff. All words are informative, and it efficiently states the operation and its scope without redundancy.

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

Completeness2/5

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

With no output schema or annotations, the description alone must support safe invocation. It omits important context such as overwrite behavior, success response, and source/destination requirements. Though parameters are fully documented, the tool's behavioral context is underspecified.

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 descriptions cover 100% of parameters (bucketName, objectName, copySource), so the description adds no additional meaning. The description does not clarify parameter interdependencies beyond what the schema already provides. Baseline 3 applies due to full schema coverage.

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?

Description uses a specific verb ('Copy') and resource ('an object in Object Storage'), and explicitly distinguishes two valid scenarios (same bucket or cross-bucket). It clearly differentiates this operation from sibling object tools like get, put, or delete.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to choose copy_object over alternative operations (e.g., get_object + put_object). No prerequisites, exclusions, or alternative tools are mentioned; the description only restates the operation without context for decision-making.

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

Deploy Server