ncloud-gov-mcp-server

ncloud_get_object_acl

Read-only

Retrieve the access control list (ACL) of an object in Object Storage to check permissions and access controls.

Instructions

Get the access control list (ACL) of an object in Object Storage

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>",
      "objectName": "<objectName>"
    },
    "name": "ncloud_get_object_acl"
  }
}

Input Schema

Name	Required	Description	Default
`bucketName`	Yes	Name of the bucket containing the object
`objectName`	Yes	Object key (path) to get ACL for

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4/5.0

Behavior3/5

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

The readOnlyHint annotation already declares the safe read-only nature, and the description does not contradict it. The description adds only the resource scope ('object in Object Storage') but no extra behavioral details like response format, required permissions, or side effects. This meets the baseline for annotation-backed tools.

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, focused sentence with no redundancy. It efficiently communicates the purpose without wasted words.

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 two-parameter read-only operation with full schema coverage, the description is largely sufficient. It identifies the resource and the action, and the annotation covers safety. The lack of an output schema is partially mitigated by the clear 'Get ACL' phrasing, though a note about the return format would make it fully 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 coverage is 100% with both parameters (bucketName and objectName) well described in the input schema. The description adds no additional parameter meaning beyond what the schema provides, 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 the operation: 'Get the access control list (ACL) of an object in Object Storage.' It uses a specific verb ('Get') and identifies the exact resource (object ACL), distinguishing it from sibling tools like ncloud_put_object_acl and ncloud_get_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 Guidelines4/5

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

The description provides clear context by specifying 'of an object' and 'Object Storage', implying this is for object-level ACL retrieval rather than bucket-level. However, it does not explicitly name alternatives or state when-not-to-use, so it stops short of a perfect score.

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

Deploy Server