ncloud-gov-mcp-server

ncloud_list_mssql_folders

Read-only

List folders in an Object Storage bucket for Cloud DB for MSSQL to manage your database storage.

Instructions

List folders within an Object Storage bucket for Cloud DB for MSSQL

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_mssql_folders"
  }
}

Input Schema

Name	Required	Description	Default
`bucketName`	Yes	Object Storage bucket name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.8/5.0

Behavior3/5

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

The readOnlyHint annotation already indicates a safe read operation, and the description does not contradict it. The description adds context about the bucket scope but does not disclose additional behavioral traits such as pagination, permission requirements, or whether folders are listed recursively.

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 sentence that is concise, front-loaded, and free of unnecessary words. It directly communicates the action and target.

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?

For a simple read-only tool with one parameter, the description is mostly complete. However, with no output schema, it does not mention the return format or clarify what 'folders' means in the object storage context, which would improve completeness.

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?

The input schema already documents bucketName with a clear description, giving 100% schema coverage. The tool description adds no further parameter semantics, so the baseline score of 3 is appropriate.

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 a specific action (list), a specific resource (folders within an Object Storage bucket), and a context (Cloud DB for MSSQL). This distinguishes it from sibling tools like ncloud_list_mssql_buckets, which list buckets rather than folders within a bucket.

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 usage: you use this tool when you need to see folders inside a specific MSSQL-related Object Storage bucket. However, it provides no explicit guidance about when not to use it or how it compares to alternatives like ncloud_list_objects or ncloud_list_mssql_buckets.

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

Deploy Server