Skip to main content
Glama

최신 기사

get_latest_articles
Read-onlyIdempotent

가장 최근 발행된 베이비뉴스 기사. category 로 분야를 좁힐 수 있다. 질문 예: "오늘 육아 뉴스", "최근 출산 정책 소식". Latest BabyNews articles.

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": "get_latest_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo개수(기본 5, 최대 10)
categoryNopolicy 사회·정책 · pregnancy 임신·출산 · health 생활·건강 · parenting 육아·교육

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds that results are the most recently published items and that category narrows them, but says nothing about ordering, default count behavior, or what happens when no articles match.

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 statement is front-loaded in the first sentence, followed by a short capability note and two illustrative queries. It is tight overall, though the trailing English echo "Latest BabyNews articles" duplicates the opening sentence without adding information.

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 two-optional-parameter read tool with no output schema and full annotation coverage, the definition supplies enough to call it correctly: what it returns, how to narrow it, and sample intents. The main missing piece is how it relates to the several sibling article-retrieval 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%, with both limit (1–10, default 5) and the category enum fully documented in the schema itself. The description only restates that category narrows the field, adding no format or behavioral detail beyond the structured definition, 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 gives a specific verb-and-resource pair — most recently published BabyNews articles — plus the fact that category narrows the field. It is clear what the tool returns, but it never distinguishes itself from siblings like get_category_articles or search_articles, so an agent must infer the boundary.

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?

The example queries ("오늘 육아 뉴스", "최근 출산 정책 소식") implicitly signal when this tool fits, namely recency-oriented news requests. However, there is no explicit when-not guidance and no named alternative such as get_category_articles for browsing by category, so the routing decision is left to inference.

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.