Skip to main content
Glama

한국일보 뉴스 (Hankookilbo)

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

list_most_read_news
Read-only

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_most_read_news"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare a safe read-only, open-world, non-destructive operation, so the bar is lower. The description still adds meaningful behavior: it returns two bundles at once (꼼꼼히 본 plus 많이 본), which an agent would not infer from the annotations or empty schema. No detail on item count or ordering, keeping it below a 5.

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?

Front-loaded with what is returned, then the usage/exclusion clause. The quoted phrase list is repetitive but serves a real disambiguation purpose for a Korean-language intent match, so it mostly 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?

With an output schema present, the description needn't explain return structure, and it correctly focuses on which bundle is fetched versus the sibling tool. Adequate for a zero-parameter read tool; minor gaps like item count or ordering are not blocking.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. No parameter-related claims are made or needed.

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?

Names a specific resource (한국일보's '꼼꼼히 본 뉴스' bundle) with a clear retrieval verb and explicitly distinguishes it from list_popular_news. The parenthetical notes it also returns '많이 본 뉴스', so an agent knows exactly what comes back.

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?

Gives concrete user phrasings that select this tool ('꼼꼼히 본', '정독할 만한 기사', '많이 본 + 꼼꼼히 본 같이 보여줘') and an explicit exclusion routing general popularity/ranking requests to list_popular_news. Both when-to-use and when-not-to-use are covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.