Skip to main content
Glama

분야별 기사

get_category_articles
Read-onlyIdempotent

분야(정책·임신출산·생활건강·육아교육)별 최근 기사. 질문 예: "최근 육아정책 변경사항"(policy), "임신 건강 기사"(pregnancy). Recent articles by section; policy covers parenting policy updates.

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": {
      "category": "<category>"
    },
    "name": "get_category_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo최근 N일(기본 365)
limitNo개수(기본 5, 최대 10)
categoryYes분야

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, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds only that 'policy' specifically covers parenting policy updates, and says nothing about recency window behavior, result ordering, or the cap of 10 beyond what the schema states.

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 with the resource stated first and examples second; nothing is padded. The closing English clause partially restates the opening Korean sentence, which is minor redundancy but aids clarity for mixed-language readers.

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 simple, read-only, three-parameter lookup with no output schema and full schema coverage, the description supplies enough for correct invocation. Only the return shape and result ordering are unstated, which is acceptable given annotations and schema richness.

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 coverage is 100% and every parameter already carries a description and defaults, so baseline is 3. The description adds modest value by giving Korean labels for the enum values (정책·임신출산·생활건강·육아교육) and a concrete question-to-category mapping, but it says nothing extra about days or limit.

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 states a specific verb+resource ('분야별 최근 기사' / 'Recent articles by section') and enumerates the four sections, so the agent knows exactly what this returns. It does not distinguish itself explicitly from siblings like get_latest_articles or search_articles, leaving that separation to inference from 'by section'.

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?

Concrete example questions are given with the category they map to ("최근 육아정책 변경사항"→policy, "임신 건강 기사"→pregnancy), which is clear when-to-use context. There are no exclusions or named alternatives telling the agent when a different tool is preferable.

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.