Skip to main content
Glama

임신·출산·육아 정보 통합 검색

search_parenting_info
Read-onlyIdempotent

질문 낱말로 Q&A(아이사랑 등 공식 출처 기반 정보)와 기사를 함께 찾는다. 기사마다 발행일이 붙는다. 질문 예: "이유식 언제 시작해요?", "아기 열 날 때", "임신 초기 증상". Korean pregnancy and parenting Q&A from official sources plus related news.

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

Input Schema

NameRequiredDescriptionDefault
limitNo각 종류별 개수(기본 3, 최대 5)
queryYes질문의 핵심 낱말(예: 이유식 시작, 예방접종 일정)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 openWorldHint=false, so the safety profile is covered. The description adds two useful facts beyond that — results mix two source types and each article carries a publish date — but says nothing about result ordering, ranking, or what happens when one source type has no matches.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and the example questions are efficient, but the trailing English sentence restates the Korean purpose line verbatim in another language, which duplicates rather than adds. Two of the four sentences carry most of the value.

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 only two parameters, full schema coverage, no output schema and annotations covering safety, the definition supplies what an agent needs: what is searched, that results span two source types, and that articles expose publish dates. Minor gaps around ranking and empty-result behavior keep it from a 5.

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 the schema already explains both query ('질문의 핵심 낱말') and limit ('각 종류별 개수, 기본 3, 최대 5'). The description's example questions reinforce the query phrasing but add no constraint or syntax beyond the schema, 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?

The first sentence states a specific verb and resource set: find Q&A (official-source, e.g. 아이사랑) and articles 'together' by question keywords. The word 'together' implicitly distinguishes it from the single-source siblings search_qa and search_articles, but no sibling is named explicitly.

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 example questions ("이유식 언제 시작해요?", "아기 열 날 때"), which shows the intended natural-question input style. There is no statement of when to prefer this over search_qa/search_articles, and no exclusions or prerequisites.

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.