Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_ncs_list_objects

Read-only

List objects in a Ncloud Storage bucket using pagination, prefix, delimiter, and start-after filters; each returned entry includes its storage class.

Instructions

[Ncloud Storage] List objects in a Ncloud Storage bucket (GET /?list-type=2). Supports prefix, delimiter, maxKeys, startAfter and continuation-token pagination; each entry includes its storage class.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
prefixNoLimits results to keys beginning with this prefix
maxKeysNoMaximum number of keys to return (1–1,000, default 1,000)
delimiterNoDelimiter for grouping keys (commonly '/')
bucketNameYesName of the Ncloud Storage bucket
startAfterNoStart listing after this key
continuationTokenNoPagination: nextContinuationToken of the previous response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.15.0
    • changedInput schema / properties / bucketName / description
      Previous value: -"Name of the bucket"New value: +"Name of the Ncloud Storage bucket"
    • changedInput schema / properties / continuationToken / description
      Previous value: -"Token for pagination (from previous response's nextContinuationToken)"New value: +"Pagination: nextContinuationToken of the previous response"
    • changedInput schema / properties / maxKeys / description
      Previous value: -"Maximum number of keys to return (default 1000)"New value: +"Maximum number of keys to return (1–1,000, default 1,000)"
    • addedInput schema / properties / maxKeys / maximum
      Added value: +1000
    • addedInput schema / properties / maxKeys / minimum
      Added value: +1
    • changedInput schema / properties / maxKeys / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / startAfter
      Added value: +{
+  "description": "Start listing after this key",
+  "type": "string"
+}
  2. First observedv1.10.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is known. The description adds behavioral context beyond that: it is a paginated list operation with prefix/delimiter grouping, startAfter support, and continuation-token traversal, plus the storage class is included in each returned entry. No contradiction with annotations.

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?

Two dense sentences with zero filler. The main action and resource are front-loaded, and the second sentence compactly enumerates all relevant capabilities. Every phrase contributes useful information.

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?

With no output schema, the description should cover return expectations; it mentions storage class inclusion, which is useful, but does not describe other returned fields (e.g., key, size, last modified) or truncation behavior. Overall it gives an agent enough to invoke the tool correctly, though fuller response details would make it complete.

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 baseline applies. The description merely names the same parameters found in the schema (prefix, delimiter, maxKeys, startAfter, continuation-token) without adding new semantic details such as default behavior or format expectations. It adds no value beyond what the input schema already provides.

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?

States a specific verb and resource: 'List objects in a Ncloud Storage bucket' with the exact REST endpoint (GET /?list-type=2). The 'Ncloud Storage' scope and 'objects in a bucket' target clearly distinguish it from siblings like ncloud_ncs_list_buckets and ncloud_ncs_list_object_versions, and the added note about storage class per entry removes ambiguity.

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 clearly implies how to use the tool by enumerating supported filtering and pagination parameters, but it never explicitly states when to choose this tool over alternatives such as ncloud_ncs_list_object_versions or the legacy ncloud_list_objects. There are no exclusions or alternative routing cues, so the agent must infer the correct context from the 'Ncloud Storage' prefix.

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