ncloud-gov-mcp-server

ncloud_put_bucket_versioning

Set the versioning state of an object storage bucket to Enabled or Suspended, controlling version retention and rollback capabilities.

Instructions

Set the versioning state of an Object Storage bucket (Enabled or Suspended)

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>",
      "status": "<status>"
    },
    "name": "ncloud_put_bucket_versioning"
  }
}

Input Schema

Name	Required	Description	Default
`status`	Yes	Versioning status to set (Enabled \| Suspended)
`bucketName`	Yes	Name of the bucket

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.5/5.0

Behavior2/5

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

Annotations are empty, so the description carries full burden for behavioral disclosure. It only states the action 'Set' without mentioning side effects, necessary permissions, reversibility, or consequences of changing versioning. As a mutation tool, this is a significant gap.

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?

The description is a single, concise sentence that front-loads the verb 'Set' and directly states the resource and allowed values. There is no unnecessary information or padding.

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?

The tool is simple with only two parameters and no output schema, so the description is minimally viable. However, as a mutation tool without annotations, it lacks behavioral context, usage guidance, and any mention of prerequisites or return behavior, leaving gaps.

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 coverage is 100% (both parameters have descriptions), so the baseline is 3. The description adds minimal value beyond restating the status enum and the bucket name, which the schema already documents. No additional parameter semantics are provided.

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 the action 'Set' and the specific resource 'versioning state of an Object Storage bucket', with the allowed values '(Enabled or Suspended)' explicitly listed. This distinguishes it from sibling tools like ncloud_get_bucket_versioning, which reads the state, and other bucket operations.

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 implies the tool is for changing versioning state, but it does not explicitly state when to use it, prerequisites, or alternatives. It offers no exclusions or when-not-to-use guidance, so the agent must infer usage from the verb and resource.

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

Deploy Server