Skip to main content
Glama

한국일보 뉴스 (Hankookilbo)

최신 뉴스

list_latest_news
Read-only

'최신 기사', '방금 올라온 뉴스', '새로 나온 기사', '오늘 새 기사'처럼 최근 발행 순서대로 기사를 볼 때 사용합니다. page_num 으로 다음 페이지를 더 가져올 수 있습니다.

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_latest_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_numNo페이지 번호(1부터). 1=가장 최신.
page_sizeNo가져올 기사 수(1~최대치로 클램프).

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is fully covered structurally. The description adds only the pagination affordance ('page_num 으로 다음 페이지를 더 가져올 수 있습니다'), with nothing about result volume caps or what happens past the last page.

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?

Two short sentences: trigger examples first, paging hint second — front-loaded and waste-free. The list of four near-synonymous Korean phrases is slightly redundant but serves as retrieval vocabulary.

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?

For a zero-required-parameter, read-only listing tool with full schema coverage and an output schema, the description covers ordering and paging adequately; return values need not be explained. The only real gap is disambiguation from the many sibling news-listing tools.

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?

Schema description coverage is 100% and both parameters are documented there, including 'page_num' starting at 1 = newest. The description restates the paging behavior without adding format, limits, or clamping details beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description makes clear this returns articles in reverse-chronological publication order ('최근 발행 순서대로 기사를 볼 때'), which is a specific ordering contract, not just 'news'. However, it never names or contrasts the crowded sibling set (list_top_headlines, list_timely_news, list_most_read_news, list_popular_news), so the ordering distinction must be inferred.

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?

It anchors usage to concrete user phrasings ('최신 기사', '방금 올라온 뉴스', '오늘 새 기사'), which is a strong trigger signal for an agent routing a request. It gives no explicit when-not or alternative-tool guidance, so exclusions are left implicit.

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.