Skip to main content
Glama

베이비뉴스 기사 검색

search_articles
Read-onlyIdempotent

베이비뉴스 기사를 뜻(자연어 질문)과 낱말로 함께 찾는다(최근 3년은 의미 검색). 임신·출산·육아·정책·교육·건강 기사. 제목·키워드·요약에서 찾아 제목·발행일·기자·요약·원문 주소를 돌려준다(전문은 주소에서). 질문 예: "2026년 육아휴직 급여 바뀐 점", "어린이집 급식 기준 기사", "유보통합 최신 소식". Korean pregnancy, childbirth, parenting and family policy news articles with publish/update dates and URLs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo최근 N일 안 기사만(선택, 기본 730, 최대 3650)
modeNo검색 방식: hybrid(기본, 뜻과 낱말을 함께, 의미 검색은 최근 3년) · semantic(뜻) · keyword(낱말)
limitNo돌려줄 개수(기본 5, 최대 10)
queryYes찾을 낱말(예: 부모급여, 유보통합)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real context beyond them: it discloses which fields are searched (제목·키워드·요약), which fields are returned (제목·발행일·기자·요약·원문 주소), and that full text is not included and must be fetched from the URL, plus the three-year ceiling on semantic matching.

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 core capability, scope and return fields are front-loaded, and the example questions make the expected query style concrete without bloat. The trailing English sentence largely repeats the Korean content, which is mildly redundant but justified for cross-language agents.

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 read-only search tool with full schema coverage and no output schema, the description supplies the missing return-value information itself (fields returned, full text excluded) and marks the semantic time window. Only the boundaries with sibling retrieval tools remain unstated.

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%, so the schema already documents all four parameters including defaults, maximums and the mode enum. The description restates that hybrid combines meaning and words and that semantic search is limited to the recent three years, which echoes the schema rather than adding new syntax or format guidance, so 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?

States a concrete verb (찾는다/search) plus the specific resource (베이비뉴스 기사) and scope (임신·출산·육아·정책·교육·건강), and the hybrid meaning+keyword approach distinguishes it from the listing siblings such as get_latest_articles or get_category_articles. It stops short of naming a sibling to redirect to, so it is clear but not fully differentiated.

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

Usage Guidelines3/5

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

Usage is implied through three concrete example queries and the note that semantic search only covers the last three years, which tells an agent what kinds of inputs fit. There is no explicit when-not or named alternative (e.g. use get_article for full text, or get_latest_articles for browsing), and '전문은 주소에서' only hints at routing rather than stating it.

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.