Skip to main content
Glama
Sign In
ncloud-mcp-server

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_vodstation_update_channel

Idempotent

Update a VOD Station streaming channel's name, protocols, segment settings, and DRM by replacing the current configuration with the full desired state.

Instructions

Update a VOD Station streaming channel's details (name, protocols, segment settings, encryption/DRM). This is a PUT that replaces the channel configuration, so provide the full desired state.

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": {
      "channelId": "<channelId>",
      "channelName": "<channelName>",
      "protocolList": "<protocolList>",
      "segmentDuration": "<segmentDuration>"
    },
    "name": "ncloud_vodstation_update_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
drmNoMulti-DRM configuration
channelIdYesChannel ID to update (e.g., vs-20250821095732-xxxxxxx)
channelNameYesChannel name (3-20 chars, alphanumeric + hyphen). Sent as the API 'name' field
protocolListYesStreaming protocols (HLS, DASH)
encryptionListNoContent protection (encryption) settings per protocol
segmentDurationYesPlayback seconds per segment (5-20)
segmentDurationOptionNoSegmentation method: BASIC (default, regular intervals) or VARIABLE (keyframe-based)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations indicate idempotentHint=true and destructiveHint=false. The description adds that it uses PUT and replaces configuration, which is consistent and provides additional behavioral context beyond the annotations.

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 two sentences, efficient, and front-loaded with key information: action, resource, and behavioral note. No unnecessary 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 7-parameter tool with nested objects and no output schema, the description covers the essential behavioral note (full state required). It could mention expected response or error handling, but given annotations and schema coverage, it is fairly 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 description coverage is 100%, so the schema explains each parameter. The description groups parameters into categories but does not add new semantics or explanations beyond the schema. Baseline 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 tool updates a VOD Station channel's details, listing the categories (name, protocols, segment settings, encryption/DRM). It distinguishes from sibling tools like create, delete, start, stop by focusing on update and noting it's a PUT replacement.

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 explicitly notes 'This is a PUT that replaces the channel configuration, so provide the full desired state,' giving a critical usage guideline. It could be improved by mentioning reading current state via get_channel first, but the guidance is clear.

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

Deploy Server

Other Tools