ncloud-gov-mcp-server

ncloud_drm_create_policy

Create a DRM policy to configure Widevine, PlayReady, and FairPlay security settings, controlling license durations, HDCP levels, and offline playback permissions.

Instructions

Create a new DRM policy with Widevine / PlayReady / FairPlay security settings

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": {
      "policyName": "<policyName>",
      "persistent": "<persistent>",
      "rentalDuration": "<rentalDuration>",
      "playbackDuration": "<playbackDuration>",
      "drmPolicyConfig": "<drmPolicyConfig>"
    },
    "name": "ncloud_drm_create_policy"
  }
}

Input Schema

Name	Required	Description
`persistent`	Yes	Offline license retention (must be true if using rentalDuration)
`policyName`	Yes	Policy name (3-20 chars: letters, numbers, '_')
`rentalDuration`	Yes	Seconds until first playback must start after license acquisition (0~2147483647, default 0)
`drmPolicyConfig`	Yes	Per-DRM policy settings (widevine/playready/fairplay)
`playbackDuration`	Yes	License validity in seconds from first playback (0~2147483647, default 0)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.6/5.0

Behavior2/5

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

Annotations only declare destructiveHint=false. The description adds minimal behavioral context beyond the creation action itself. It does not disclose prerequisites (e.g., needing an existing site), side effects, permissions required, or return value behavior. With sparse annotations, the description carries a heavier burden that it fails to meet.

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 essential action and resource. Every word earns its place, with no unnecessary filler.

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?

Despite a complex schema with nested objects and no output schema, the description offers only a high-level summary. It does not mention the hierarchical structure (drmPolicyConfig containing per-DRM settings), any prerequisites like site creation, or expected results. The schema does a lot of heavy lifting, but the description leaves key contextual gaps.

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%, so all parameters and nested properties are already well documented. The description's mention of 'security settings' adds no additional meaning beyond what the schema already provides, keeping this at the baseline score.

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 action ('Create') and the resource ('a new DRM policy'), and specifies the three DRM security systems (Widevine / PlayReady / FairPlay). This distinguishes it from sibling tools like ncloud_drm_update_policy or ncloud_drm_delete_policy.

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 clearly indicates this is for creating a new policy (as opposed to updating/deleting existing ones), providing a clear usage context. However, it does not explicitly mention alternatives or when not to use it, which prevents 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