ncloud-gov-mcp-server

ncloud_get_bucket_acl

Read-only

Retrieve the access control list (ACL) for an Object Storage bucket to view its permissions and access settings.

Instructions

Get the access control list (ACL) of 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_get_bucket_acl"
  }
}

Input Schema

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

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. The description adds the context that this targets Object Storage buckets, but discloses no additional behavioral traits such as response format, permissions required, or error conditions. It is consistent with the annotation, with 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 is front-loaded with the action and resource. It contains no filler or redundant information, making it efficiently sized for its simple purpose.

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?

Given the low complexity (one parameter, no output schema, read-only annotation), the description covers the essential purpose and resource. It lacks detail on the return value structure or potential errors, but for such a straightforward read operation, the minimal context is largely sufficient.

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 provides 100% coverage for the single parameter (bucketName) with a clear description 'Name of the bucket'. The tool description adds no extra parameter semantics beyond what the schema already offers, so the high schema coverage warrants a baseline score of 3.

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 'Get the access control list (ACL) of an Object Storage bucket' clearly states a specific verb (Get) and resource (ACL of an Object Storage bucket). It explicitly distinguishes the bucket-level ACL tool from sibling tools like get_object_acl and put_bucket_acl.

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?

No explicit guidance on when to use this tool versus alternatives is provided. However, the phrase 'Get the access control list of an Object Storage bucket' implies its use case: whenever you need to retrieve a bucket's ACL. This is an implied usage but lacks direct comparisons or exclusions.

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

Deploy Server