Skip to main content
Glama

한국일보 뉴스 (Hankookilbo)

by com.hankookilbo.mcp

많이 본 인기 뉴스 (분야/전체)

list_popular_news
Read-only

'인기 뉴스', '많이 본 기사', '오늘 가장 많이 본 뉴스', '핫한/화제의 기사', '지금 뜨는 뉴스'처럼 조회수 기준 인기(많이 본) 순위는 기본적으로 이 도구입니다. section_cd='all'이면 사이트 전체, 분야 코드를 넣으면 해당 분야 인기 기사입니다(예: section_cd='politics' = 정치 인기 기사). 이것이 조회수 기반 인기 순위이며, 편집부 추천(list_recommended_articles)과 구분됩니다. 사용자가 콕 집어 '꼼꼼히 본 뉴스'를 원할 때만 list_most_read_news 를 쓰세요. 전체 조회 시 exclude_section_cd 로 특정 분야를 제외할 수 있습니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_sizeNo가져올 기사 수(1~최대치로 클램프).
section_cdNo섹션 코드 슬러그(소문자). 'all'=사이트 전체. list_sections 참고.all
exclude_section_cdNosection_cd='all' 전체 조회 시 제외할 섹션 코드 슬러그.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo페이징 메타데이터(있을 때).
itemsNo기사 카드 목록.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations (readOnlyHint=true, openWorldHint=true) already inform the agent that this is a safe, read-only operation. The description adds behavioral context by clarifying the ranking is view-count based and not editor-curated, which is valuable 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is informative but slightly verbose. It front-loads the key purpose and includes necessary differentiation, but could be more concise. However, it avoids redundancy and each sentence adds value.

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 three optional parameters, an output schema, and annotations, the description covers the core functionality, usage context, parameter semantics, and sibling differentiation. It is sufficiently complete for an agent to select and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, the baseline is 3. The description adds meaning by explaining that section_cd='all' covers the entire site, that exclude_section_cd only works with 'all', and referencing list_sections for code discovery. This goes beyond the schema's minimal descriptions.

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 identifies the tool as returning popular news based on view count, specifies the resource (popular news) and verb (list), and distinguishes it from sibling tools like list_recommended_articles and list_most_read_news. Examples like '인기 뉴스', '많이 본 기사' reinforce its purpose.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool (view-count-based popular news) and distinguishes it from list_recommended_articles (editor recommendations) and list_most_read_news (for '꼼꼼히 본 뉴스'). It also explains how to use section_cd and exclude_section_cd parameters.

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

All 한국일보 뉴스 (Hankookilbo) toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a distinct purpose: horoscopes (daily vs MBTI), news listings (latest, most read, popular, recommended, timely, top headlines), sections, and search. Descriptions provide clear usage examples and explicitly differentiate similar-sounding tools like list_most_read_news (editor-curated) vs list_popular_news (view-count based).

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case: get_ for horoscopes, list_ for various news lists and sections, and search_ for search. No mixing of camelCase or other conventions.

Tool Count5/5

10 tools is appropriate for a news server. It covers the main news consumption patterns (latest, popular, recommended, by section, search) plus two specialized horoscope tools. Neither too sparse nor overwhelming.

Completeness5/5

The tool surface covers typical news site operations: browsing latest, popular (both view-based and editor-curated), by category, headlines, time-based recommendations, and search. Horoscope retrieval is an extra feature. The missing article text retrieval is intentional (metadata-only return). No obvious gaps for the intended domain.

Resources