ncloud-gov-mcp-server

ncloud_list_object_versions

Read-only

List all versions of objects in a versioning-enabled bucket. Use prefix, delimiter, and pagination markers to filter and page through version history.

Instructions

List all versions of objects in a versioning-enabled Object Storage bucket

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

Input Schema

Name	Required	Description
`prefix`	No	Limits results to keys beginning with this prefix
`maxKeys`	No	Maximum number of keys to return (default 1000)
`delimiter`	No	Delimiter for grouping keys (commonly '/')
`keyMarker`	No	Key marker for pagination
`bucketName`	Yes	Name of the bucket
`versionIdMarker`	No	Version ID marker for pagination (used with keyMarker)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description is consistent with this. The description adds the useful context that this operation lists ALL versions and requires versioning-enabled, but it does not disclose pagination behavior, potential large result sets, or what happens when versioning is disabled. This is adequate but not rich.

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 immediately states the tool's purpose. It is front-loaded with the action and resource, and every word earns its place. There is no redundant or vague wording.

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

Completeness4/5

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

The description is sufficiently complete for a simple listing operation. It includes the key condition (versioning-enabled), and the schema fully describes all parameters. Without an output schema, the return format is not explained, but for a list operation this is not a major gap. The annotation and schema cover the rest.

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% for all 6 parameters, so the schema fully documents each parameter. The description does not add any additional meaning beyond what the schema provides, matching the baseline for high schema coverage.

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 uses the specific verb 'List' with the resource 'all versions of objects in a versioning-enabled Object Storage bucket'. It clearly distinguishes this tool from sibling ncloud_list_objects by focusing on object versions rather than current objects, and it correctly identifies the required bucket configuration.

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?

The description explicitly states the prerequisite that the bucket must be versioning-enabled, which gives clear context for when to use this tool. It does not mention alternatives or exclusions, but the purpose is unambiguous and the required condition is stated.

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

Deploy Server