ncloud-gov-mcp-server

ncloud_sourcedeploy_get_objectstorage_objects

Read-only

Retrieves the list of objects stored in a specified Object Storage bucket, enabling you to view and manage its contents.

Instructions

Get the list of objects in an 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_sourcedeploy_get_objectstorage_objects"
  }
}

Input Schema

Name	Required	Description	Default
`bucketName`	Yes	Name of the Object Storage bucket

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The readOnlyHint annotation already signals this is a safe read operation. The description adds minimal behavioral context by indicating that a list is returned, but it does not disclose pagination, ordering, permissions, or any other operational nuances. It is consistent with the annotation, so no contradiction.

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 conveys the tool's purpose. There is no redundant wording or unnecessary detail.

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 one-parameter read-only tool with full schema coverage and a readOnlyHint annotation, the description is largely sufficient. It clearly states what is returned (a list of objects) and the only required input is well-documented. Some guidance about pagination or relationship to generic Object Storage tools would improve it, but this is not critical for such a basic operation.

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 fully covers the single parameter 'bucketName' with a description 'Name of the Object Storage bucket'. The tool description merely echoes this by saying 'in an Object Storage bucket', adding no additional semantic explanation beyond the schema.

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 verb 'Get' and the resource 'list of objects in an Object Storage bucket'. It differentiates from sibling tools like ncloud_sourcedeploy_get_objectstorage_buckets (which lists buckets) and ncloud_list_objects (which is a more generic Object Storage list operation).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives such as ncloud_list_objects or ncloud_get_object. It only states what the tool does, leaving the agent to infer appropriate usage from the tool name alone.

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

Deploy Server