Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_ncs_list_buckets

Read-only

List Ncloud Storage buckets in your Naver Cloud account, using prefix filters and pagination to locate S3-compatible object storage resources quickly.

Instructions

[Ncloud Storage] List Ncloud Storage buckets (GET / on kr.ncloudstorage.com). Ncloud Storage is the newer S3-compatible object storage at {bucket}.kr.ncloudstorage.com (KR only) and is a separate service from the legacy Object Storage (kr.object.ncloudstorage.com) with its own bucket namespace — for Object Storage buckets use ncloud_list_buckets and the other ncloud_* tools without the ncs_ prefix.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
prefixNoOnly buckets whose name starts with this prefix
maxBucketsNoBuckets per page (1–10,000)
continuationTokenNoPagination: continuationToken from the previous response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.15.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / continuationToken
      Added value: +{
+  "description": "Pagination: continuationToken from the previous response",
+  "type": "string"
+}
    • addedInput schema / properties / maxBuckets
      Added value: +{
+  "description": "Buckets per page (1–10,000)",
+  "maximum": 10000,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / prefix
      Added value: +{
+  "description": "Only buckets whose name starts with this prefix",
+  "type": "string"
+}
  2. First observedv1.10.1

TDQS

A4.4/5.0
Behavior4/5

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

The readOnlyHint annotation already indicates this is a safe read operation. The description adds valuable context about the service distinction (newer S3-compatible vs legacy Object Storage) and the separate bucket namespace, which is important behavioral context beyond the annotation. It doesn't describe pagination or return format, but the annotation covers the safety profile and the description adds the key scoping context.

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, information-dense sentence that front-loads the core purpose and endpoint, then adds the critical service distinction and routing guidance. Every clause earns its place; there is no redundancy or filler.

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 read-only list operation with a fully documented schema and readOnlyHint annotation, the description is nearly complete. It covers the service distinction, endpoint, and routing to the correct sibling. The only minor gap is that it doesn't describe the response format or pagination behavior, but the schema's continuationToken parameter implies pagination and the output schema is absent, so this is a minor omission.

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%, so the schema already documents all three parameters (prefix, maxBuckets, continuationToken) with descriptions. The description doesn't add additional parameter semantics beyond what the schema provides, so the baseline 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 states a specific verb ('List'), a specific resource ('Ncloud Storage buckets'), and the exact API endpoint (GET / on kr.ncloudstorage.com). It also explicitly distinguishes this tool from the legacy Object Storage service and names the sibling tool (ncloud_list_buckets) to use instead, making it unambiguous.

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?

The description explicitly states when to use this tool (for the newer S3-compatible Ncloud Storage service) and when not to (for legacy Object Storage, use ncloud_list_buckets and other ncloud_* tools without the ncs_ prefix). This is clear, actionable guidance that prevents incorrect tool selection.

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