mcp-chzzk

get_live_status

Retrieve a Chzzk channel's live status including broadcast activity, title, category, viewer count, and start time.

Instructions

Get the lightweight live status for a Chzzk channel — whether it is currently broadcasting, title, category, viewer counts, start time.

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": {
      "channel": "<channel>"
    },
    "name": "get_live_status"
  }
}

Input Schema

Name	Required	Description	Default
`channel`	Yes	Chzzk channel — either a 32-hex channel id or a chzzk.naver.com URL (e.g. https://chzzk.naver.com/live/<id>).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 27, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It adequately states the tool is lightweight and lists returned data. However, it does not disclose any potential side effects, authentication needs, or rate limits. For a read-only status tool, this is acceptable but leaves expectations implicit.

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 that front-loads the purpose and lists key outputs. Every word adds value, with no redundancy or unnecessary detail.

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?

Given the tool has one required parameter and no output schema, the description adequately covers what the tool does and what it returns. It could benefit from specifying the return type (e.g., JSON object) or field types, but the listed fields (broadcasting, title, etc.) provide sufficient context for an AI agent.

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?

The schema description coverage is 100% (the parameter 'channel' is described with both id and URL format). The description adds context that the tool is for Chzzk channels but does not add significant meaning 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 retrieves 'lightweight live status' for a Chzzk channel and enumerates the specific fields returned (broadcasting, title, category, viewer counts, start time). This distinguishes it from siblings like get_live_detail (which likely provides more detail) and list_lives (which returns multiple channels).

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?

The description implies this tool is for lightweight status checks, but does not explicitly state when to choose it over get_live_detail or list_lives. No exclusion criteria or alternative recommendations are provided.

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

Deploy Server