Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_ncs_create_bucket

Create a Ncloud Storage bucket, optionally enabling Object Lock and versioning, with dry-run mode to preview before actual creation.

Instructions

[Ncloud Storage] Create a Ncloud Storage bucket (PUT / on {bucket}.kr.ncloudstorage.com). Bucket names: 3–63 chars, lowercase letters/digits/hyphens, start and end alphanumeric, no dots. Optionally enable Object Lock at creation (this also turns on versioning). Use dryRun=true to preview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dryRunNoIf true (default), returns a preview without actually creating the bucket
bucketNameYesName of the bucket to create
objectLockEnabledNoSend x-amz-bucket-object-lock-enabled: true — enables Object Lock (WORM) and versioning on the new bucket. Cannot be enabled later on an existing bucket through this header

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.15.0
    • addedInput schema / properties / bucketName / pattern
      Added value: +"^[a-z0-9][a-z0-9-]{1,61}[a-z0-9]$"
    • addedInput schema / properties / objectLockEnabled
      Added value: +{
+  "default": false,
+  "description": "Send x-amz-bucket-object-lock-enabled: true — enables Object Lock (WORM) and versioning on the new bucket. Cannot be enabled later on an existing bucket through this header",
+  "type": "boolean"
+}
  2. First observedv1.10.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations carry only destructiveHint=false, so the description carries most of the behavioral burden. It does add genuine value by disclosing a non-obvious side effect — enabling Object Lock 'also turns on versioning' — and by pointing to the dry-run preview path. It does not disclose failure behavior (e.g., bucket name already taken), permission/authentication requirements, or what a successful call returns.

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?

Four sentences with the core purpose front-loaded; each sentence has a job: purpose/endpoint, naming constraints, the Object Lock side effect, and the preview suggestion. Minor redundancy — the '[Ncloud Storage]' prefix plus 'Ncloud Storage bucket' is slightly repetitive, and the naming sentence partly duplicates schema/pattern info — but overall it is tight and scannable.

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?

Adequate for a simple 3-param tool with full schema coverage and no nested objects: the description covers purpose, naming rules, the Object Lock/versioning side effect, and the preview safety valve. It is incomplete on outcome shape (there is no output schema, and the description says nothing about the response) and on failure semantics (existing bucket, invalid name) — both relevant for a creating 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 description coverage is 100%, so the baseline is 3. The description adds readable naming rules (3–63 chars, no dots) that translate the regex pattern into prose, which has marginal value, but it largely re-expresses what the schema already encodes (pattern, dryRun default/behavior, objectLockEnabled header). It adds no meaning beyond the schema for any parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource: 'Create a Ncloud Storage bucket' and pins it to an exact endpoint, 'PUT / on {bucket}.kr.ncloudstorage.com' — clearly identifying the S3-compatible NCS API. This distinguishes it from list/head/delete siblings such as ncloud_ncs_list_buckets and ncloud_ncs_delete_bucket, and the NCS framing signals it apart from the classic ncloud_create_bucket sibling. However, it never explicitly names or contrasts that sibling, so differentiation is implicit.

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?

Usage guidance is implied rather than explicit: 'Use dryRun=true to preview' hints that the agent should preview before committing a real creation. But there is no when-to-use vs alternatives — notably, when to choose this over the sibling ncloud_create_bucket — and no exclusions, prerequisites, or permission context.

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