Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_ncs_put_bucket_lifecycle

Set or replace Ncloud Storage bucket lifecycle rules for current/noncurrent version transitions and expiration. mergeWithExisting preserves omitted rules; dryRun previews changes.

Instructions

[Ncloud Storage] Set lifecycle rules on a Ncloud Storage bucket (PUT /?lifecycle). Supports current-version transitions (ONEZONE_IA | DEEP_ARCHIVE) and expiration by days or date, plus NoncurrentVersionTransition / NoncurrentVersionExpiration for versioning-enabled buckets. ⚠️ The API replaces the ENTIRE configuration on every call — a rule left out disappears. Default mergeWithExisting=false replaces (the response lists the rules that were removed); mergeWithExisting=true reads the current rules first and keeps those whose id you did not resend. Use dryRun=true to preview the exact XML.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rulesYesLifecycle rules to apply
dryRunNoIf true, returns the XML that would be sent and what would change, without applying
bucketNameYesName of the bucket to set lifecycle configuration for
mergeWithExistingNotrue: keep existing rules whose id is not in `rules` (same-id rules are replaced). false (default): the configuration becomes exactly `rules`

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.15.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations are empty, so the description carries full burden. It discloses the destructive replace-on-every-call behavior, explains merge semantics, mentions the response lists removed rules, and flags the abortIncompleteMultipartUploadDays spec mismatch. These are critical behavioral traits beyond the schema.

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?

The description is dense but appropriately so for a complex API. It front-loads the purpose and the most critical warning (replaces entire config), then details merge and dryRun. While long, every sentence contributes essential information without fluff.

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 tool with nested rules, multiple storage classes, and versioning options, the description covers all major gotchas: replace behavior, merge semantics, dryRun, unsupported AWS names, and the abortIncompleteMultipartUploadDays risk. It is complete for an agent to call correctly, even without an output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant extra meaning: the replace-vs-merge behavior for the rules parameter, dryRun's preview capability, and the specific enum restrictions (ONEZONE_IA/DEEP_ARCHIVE, not STANDARD_IA/GLACIER). It enriches the schema's parameter descriptions with operational caveats.

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 it sets lifecycle rules on a Ncloud Storage bucket via PUT /?lifecycle, enumerates supported features (transitions, expiration, noncurrent versions), and distinguishes itself from sibling get/delete lifecycle tools. The verb-resource pair is explicit and specific.

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

Usage Guidelines5/5

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

It provides explicit guidance on when to use the tool and the critical distinction between mergeWithExisting=false (replaces) and true (keeps existing rules), plus dryRun for preview. It also warns about unsupported AWS storage class names and the potential rejection of abortIncompleteMultipartUploadDays, giving clear operational 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