Skip to main content
Glama

한국일보 뉴스 (Hankookilbo)

by com.hankookilbo.mcp

꼼꼼히 본 뉴스 (+ 많이 본)

list_most_read_news
Read-only

한국일보 홈이 '꼼꼼히 본 뉴스'로 따로 선정해 보여주는 묶음을 가져옵니다('많이 본 뉴스'도 함께 반환). '꼼꼼히 본 뉴스', '정독할 만한 기사', '많이 본 말고 꼼꼼히 본 거', '많이 본 + 꼼꼼히 본 같이 보여줘'처럼 이 '꼼꼼히 본' 묶음을 콕 집어 원할 때만 사용합니다. 그냥 '인기/많이 본/화제' 기사나 분야별 인기, 조회수 랭킹은 이 도구가 아니라 list_popular_news 를 쓰세요.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
best_itemsNo많이 본(조회수) 뉴스 기사 목록.
careful_itemsNo한국일보 홈이 '꼼꼼히 본 뉴스'로 선정한 묶음 기사 목록.

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, indicating safe read operation and possibly dynamic content. Description adds that both '꼼꼼히 본 뉴스' and '많이 본 뉴스' are returned. No contradictions. With good annotation coverage, the description adds minor but useful behavioral context.

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?

Two sentences, no wasted words. Front-loaded with purpose and return value. Highly concise and effective.

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

Completeness5/5

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

Tool is simple with no parameters and an output schema present. Description fully explains what the tool returns and when to use it, differentiating from sibling tools. Complete for the tool's complexity.

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?

No parameters. Schema description coverage is 100% (empty schema). Baseline for 0 parameters is 4. Description does not need to add parameter info because there are none.

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 fetches the '꼼꼼히 본 뉴스' curated set from the Korea Times homepage, also returning '많이 본 뉴스'. It distinguishes itself from list_popular_news by specifying that this tool is for the curated set, not general popular news.

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?

Explicitly instructs when to use (when user asks for '꼼꼼히 본' bundle) and when not to (for general popular news, use list_popular_news). Provides specific query examples and alternatives.

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