ncloud-gov-mcp-server

ncloud_set_nas_volume_access_control

Idempotent

Set access control for a NAS volume instance by specifying allowed server instances or custom IP lists.

Instructions

Set access control for a NAS volume instance (server-based or custom IP-based)

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": {
      "nasVolumeInstanceNo": "<nasVolumeInstanceNo>"
    },
    "name": "ncloud_set_nas_volume_access_control"
  }
}

Input Schema

Name	Required	Description
`customIpList`	No	List of custom IPs to allow access
`nasVolumeInstanceNo`	Yes	NAS volume instance number
`serverInstanceNoList`	No	List of server instance numbers to allow access

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations (idempotentHint=true, destructiveHint=false) are consistent with the description, but the description adds no extra behavioral context. It does not disclose whether this overwrites the entire access control list, what happens to existing rules, or any side effects. Given the 'set' semantics, this is a significant omission.

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 with a clarifying parenthetical. It is front-loaded and contains no fluff or redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no output schema and optional parameters, the description is too brief. It fails to explain the full replacement behavior, usage context, or expected response. The existence of sibling add/remove tools makes the 'set' semantics ambiguous without further explanation.

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%, so each parameter already has a description. The description's phrase 'server-based or custom IP-based' maps to the two list parameters but adds minimal extra meaning. It does not clarify whether at least one list is required or if both can be combined, which would be valuable given neither is explicitly required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Set') and the resource ('NAS volume instance'), and distinguishes the two access control types (server-based or custom IP-based). However, it does not explicitly differentiate from sibling tools like ncloud_add_nas_volume_access_control or ncloud_remove_nas_volume_access_control, leaving the 'set' vs 'add/remove' ambiguity unresolved.

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 compared to the add/remove variants. There is no mention of whether this replaces existing rules, whether both lists can be used together, or any prerequisites or conditions. The agent is left to infer usage from the tool name and sibling tools.

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

Deploy Server