Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425

ncloud_ncs_copy_object

Copy an object between Ncloud Storage buckets or paths, optionally setting its storage class to STANDARD, ONEZONE_IA, or DEEP_ARCHIVE for cost optimization.

Instructions

Copy an object within Ncloud Storage. Optionally sets the copy's storage class (STANDARD | ONEZONE_IA | DEEP_ARCHIVE)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesDestination object key (path)
bucketNameYesDestination bucket name
copySourceYesSource object path in format: /{sourceBucket}/{sourceKey}
storageClassNoStorage class for the copy — STANDARD (default): Standard Class | ONEZONE_IA: One Zone-IA (Infrequent Access) Class | DEEP_ARCHIVE: Archive Class. Sent as the x-amz-storage-class header; omit to use STANDARD. Copying an object onto itself with a different class is the way to change an existing object's storage class
Behavior2/5

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

No annotations are provided, and the description only states 'Copy an object' without detailing side effects, permissions required, or overwrite behavior. It does not mention idempotency or whether the copy is synchronous.

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?

Description is a single concise sentence without extraneous information. It efficiently communicates the core functionality and optional parameter.

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

Completeness3/5

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

There is no output schema, and the description does not explain expected return values or error conditions. For a simple copy operation, some additional context on result or behavior would improve completeness, but it is not severely lacking.

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?

The schema already provides detailed descriptions for all parameters, including the storageClass enum and format for copySource. Since schema coverage is 100%, the description adds no additional parameter semantics, so 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?

Description clearly states the action (copy) and resource (object in Ncloud Storage), and mentions optional storage class. Distinguishes from generic copy (ncloud_copy_object) via the NCS-specific name.

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 does not explicitly compare with alternative tools like ncloud_copy_object or state when to prefer this NCS variant. It implies usage via the name but lacks explicit guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sjk4425/ncloud-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server