Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_ncs_put_object_lock_configuration

DestructiveIdempotent

Configure Object Lock retention for an Ncloud Storage bucket: enable protection, set GOVERNANCE or COMPLIANCE mode with days or years, and preview changes with dryRun.

Instructions

[Ncloud Storage] Set the Object Lock configuration of a Ncloud Storage bucket (PUT /?object-lock). ObjectLockEnabled is always sent as Enabled; the default retention rule is optional — give mode plus exactly one of days (1-36,500) / years (1-100) to apply it to every new object, or omit mode to send no default retention. GOVERNANCE can be overridden by users with bypass permission; COMPLIANCE cannot be shortened or removed by anyone until it expires — it requires confirm=true. The bucket must have been created with objectLockEnabled=true. Use dryRun=true to preview the XML.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoDefault retention period in days, 1-36,500 (with mode; exactly one of days / years)
modeNoDefault retention mode GOVERNANCE | COMPLIANCE. Omit to set no default retention rule
yearsNoDefault retention period in years, 1-100 (with mode; exactly one of days / years)
dryRunNoIf true, returns the XML that would be sent without applying
confirmNoRequired (true) when mode=COMPLIANCE, because COMPLIANCE retention is irreversible
bucketNameYesName of the Ncloud Storage bucket

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv2.0.1
    • changedInput schema / properties / days / description
      Previous value: -"Default retention period in days (exactly one of days / years)"New value: +"Default retention period in days, 1-36,500 (with mode; exactly one of days / years)"
    • addedInput schema / properties / days / maximum
      Added value: +36500
    • addedInput schema / properties / dryRun
      Added value: +{
+  "default": false,
+  "description": "If true, returns the XML that would be sent without applying",
+  "type": "boolean"
+}
    • changedInput schema / properties / mode / description
      Previous value: -"GOVERNANCE | COMPLIANCE"New value: +"Default retention mode GOVERNANCE | COMPLIANCE. Omit to set no default retention rule"
    • changedInput schema / properties / years / description
      Previous value: -"Default retention period in years (exactly one of days / years)"New value: +"Default retention period in years, 1-100 (with mode; exactly one of days / years)"
    • addedInput schema / properties / years / maximum
      Added value: +100
    • changedInput schema / required
      Previous value: -[
-  "bucketName",
-  "mode"
-]New value: +[
+  "bucketName"
+]
  2. Addedv1.15.0

TDQS

A4.6/5.0
Behavior5/5

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

Despite annotations (idempotentHint, destructiveHint) already flagging mutability, the description adds substantial beyond-annotation context: ObjectLockEnabled is always forced Enabled, GOVERNANCE can be bypassed but COMPLIANCE is irreversible and requires confirm=true, and the bucket prerequisite. This is exactly the kind of consequence disclosure a mutation tool needs.

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?

Dense but front-loaded with the core operation before the retention-rule nuance. Some phrasing overlaps the schema's own descriptions, but for a tool with genuine GOVERNANCE/COMPLIANCE complexity the length is justified.

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

Completeness5/5

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

For a mutation tool with no output schema and annotations only marking safety, the description covers prerequisites, mode semantics, the confirm requirement, and dryRun preview. Nothing an agent needs to call it correctly is missing.

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 baseline is 3, but the description adds relational meaning not fully obvious from the schema: the mutual exclusivity of days and years with mode, the valid ranges, and that omitting mode sends no default retention rule. It clarifies how parameters interact rather than restating them.

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?

States a specific verb+resource ('Set the Object Lock configuration of a Ncloud Storage bucket') and even names the underlying API path. An agent can distinguish it from the sibling ncloud_ncs_get_object_lock_configuration without opening either schema.

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?

Gives clear conditions: the bucket must have been created with objectLockEnabled=true, and dryRun=true previews the XML without applying. It explains when to supply a default retention rule vs omit mode. It stops short of explicitly pointing to the get sibling as the read alternative, so not a full 5.

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