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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_livestation_update_channel

Idempotent

Update a Naver Cloud Live Station channel's configuration, including CDN, image quality, recording, and DVR settings. Specify the channel ID and new values to apply changes.

Instructions

Update configuration of a Live Station channel (CDN, quality, recording, DVR 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": {
      "channelId": "<channelId>"
    },
    "name": "ncloud_livestation_update_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
useDvrNoTime machine (DVR) setting
channelIdYesChannel ID to update
recordTypeNoRecording storage type
channelNameNoNew channel name (3-20 chars)
drmEnabledYnNoWhether to enable Multi DRM
qualitySetIdNoNew image quality setting ID
recordFormatNoRecording file format
immediateOnAirNoAuto-recording on stream start
recordFilePathNoRecording storage path
timemachineMinNoTime machine allowance in minutes (360)
isStreamFailOverNoWhether to enable streaming redundancy
recordBucketNameNoRecording storage bucket

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true (safe to retry) and destructiveHint=false (not destructive). Description adds that it updates settings but does not disclose behavioral traits like whether updates take effect immediately, if channel must be offline, or the response format.

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?

Single sentence with parenthetical list, immediately stating the verb and resource. No redundant words; efficient and front-loaded.

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

Completeness3/5

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

Given 12 parameters and no output schema, the description is minimal but sufficient for a high-level update tool. It lacks details on partial update behavior, return value, or state requirements, but annotations and schema fill many 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 coverage is 100% with each parameter described. The description only lists high-level categories (CDN, quality, recording, DVR) and does not add meaning beyond the schema descriptions. No elaboration on constraints or relationships between parameters.

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 configuration of a Live Station channel, listing specific areas (CDN, quality, recording, DVR settings). This distinguishes it from create, delete, get, and other sibling tools like stop/resume channel.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

No explicit guidance on when to use this vs alternatives (e.g., create_channel, start/stop_record). The description implies it's for modifying existing channel config but lacks context like prerequisite channel state or that channelId must be valid.

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