ncloud-gov-mcp-server

ncloud_set_member_server_image_sharing

Idempotent

Set sharing permissions for a member server image by replacing existing permissions with a new list of target login IDs.

Instructions

Set sharing permission for a member server image (replaces existing permissions)

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": {
      "memberServerImageInstanceNo": "<memberServerImageInstanceNo>",
      "targetLoginIdList": "<targetLoginIdList>"
    },
    "name": "ncloud_set_member_server_image_sharing"
  }
}

Input Schema

Name	Required	Description	Default
`targetLoginIdList`	Yes	List of target login IDs to set as sharing permission (replaces existing)
`memberServerImageInstanceNo`	Yes	Member server image instance number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The annotations provide idempotentHint=true and destructiveHint=false, but the description adds valuable behavior: 'replaces existing permissions', indicating that the entire permission list is overwritten. This is useful context beyond the annotations and does not contradict them.

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, well-structured sentence that front-loads the action and resource, and includes a parenthetical clarification. There is zero wasted text.

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 only 2 parameters, full schema coverage, and clear annotations, the description covers the essential operation and its replacement behavior. It doesn't mention response format or prerequisites, but for a simple set operation with no output schema, these are less critical. The description is complete enough for most use cases.

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%, with both parameters fully described (memberServerImageInstanceNo, targetLoginIdList). The tool description itself does not add additional parameter semantics; it relies on the schema, which is adequate. Baseline of 3 applies.

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 tool's action ('Set sharing permission') and target resource ('member server image'), while adding the key qualifier '(replaces existing permissions)' that distinguishes it from sibling tools like add/remove sharing. This makes the purpose specific and unambiguous.

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 phrase 'replaces existing permissions' implies this tool is for full replacement rather than incremental add/remove operations, providing clear usage context. However, it does not explicitly name alternative tools or state when not to use it, so it stops short of a 5.

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

Deploy Server