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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_vodstation_get_channel

Read-only

Retrieve detailed information about a VOD Station channel by channel ID. Get configuration, status, and metadata to resolve channel issues.

Instructions

Get detailed information about a specific VOD Station channel

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_vodstation_get_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelIdYesChannel ID (e.g., vs-20250821095732-xxxxxxx)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, and the description's 'Get' aligns with that. However, the description adds little beyond the annotation—'detailed information' is vague and doesn't disclose what fields are returned or error behavior. It doesn't contradict annotations, so a 3 is appropriate.

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 sentence of 10 words, front-loaded with the key verb and resource. No filler or redundancy; every word earns its place.

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 simple get-detail tool with one well-documented parameter and a readOnly annotation, the description is sufficient. While there's no output schema, 'detailed information' conveys the return type. It doesn't enumerate fields, but that's acceptable for this simple tool.

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%: the channelId property includes a description and example format. The description adds no additional meaning beyond restating that it targets a specific channel. Baseline 3 is correct when the schema does the heavy lifting.

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 uses the specific verb 'Get' with the resource 'detailed information about a specific VOD Station channel'. It clearly distinguishes from sibling tools like list_channels (for listing all channels) and create/delete/start/stop (for mutations), making the purpose 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 description implies usage: use this when you need details about a specific channel identified by channelId. It doesn't explicitly name alternatives or exclusions, but the sibling context (list_channels for a list) makes the use case 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