Skip to main content
Glama

한국일보 뉴스 (Hankookilbo)

by com.hankookilbo.mcp

뉴스 검색 (자연어/주제)

search_news
Read-only

어떤 주제·인물·사건에 대한 뉴스를 찾거나 '요즘 왜 이슈야', '이거 왜 화제야', '관련 기사 더 보여줘', '배경이 뭐야' 같은 질문에 답이 될 기사를 찾을 때 사용합니다. 질문의 맥락·의미로 관련 기사를 찾아 제목·링크·발행일·섹션 등 메타데이터만 반환하며, 기사 본문이나 AI 생성 답변·요약 전문은 제공하지 않습니다. 각 항목의 본문 전문은 item.url 의 한국일보 원문에서만 확인할 수 있습니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo가져올 기사 수(1~20, 기본 5).
queryYes자연어 질의. 예: '부동산 왜 이슈야', '대선 관련 기사 찾아줘', '이 사건 배경이 뭐야'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsNo관련 기사 카드 목록(관련도 내림차순).
queryYes검색에 사용한 자연어 질의.

TDQS

A4.3/5.0
Behavior4/5

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

Beyond readOnlyHint and openWorldHint, the description discloses that only metadata is returned (no full text or AI-generated summaries) and that full content requires the original URL. No contradictions with 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 well-structured with front-loaded purpose and clear limitations. It is informative without wasted sentences, though slightly verbose.

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 output schema and full input schema coverage, the description is fairly complete. It explains the main limitation (no full text) and context for use. Minor missing details like output sorting or newspaper source do not significantly detract.

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?

Schema coverage is 100% with descriptions for both parameters. The description adds value by providing example queries and clarifying the limit range (1-20).

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 searches for news based on natural language queries about topics, persons, events, and answers specific questions. It distinguishes from sibling list tools by emphasizing semantic search over curated lists.

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 provides explicit use cases (e.g., 'Why is this trending?', 'Show related articles') but does not explicitly list when not to use or compare with sibling tools. However, the context is clear.

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