Skip to main content
Glama

육아·웨딩·반려동물·보험·법률·노무 Q&A 검색

search_qa
Read-onlyIdempotent

베이비뉴스 Q&A를 찾는다. 육아(아이사랑·전문가 답변), 웨딩, 반려동물, 태아·어린이보험, 생활법령(아동학대·가정폭력·스토킹 등 법률)과 노무(공식 출처 기준, 법률 자문 아님). 질문·바로 답·출처 이름과 주소를 돌려준다. 질문 예: "펫보험 가입 나이", "육아휴직 중 퇴사하면", "청약철회 기간", "결혼식 계약금 환불". Korean Q&A on parenting, pets, weddings, insurance, law, labor and consumer issues with sources.

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

Input Schema

NameRequiredDescriptionDefault
limitNo돌려줄 개수(기본 5, 최대 10)
queryYes찾을 낱말(예: 조산, 예방접종, 펫보험)
categoryNo분야(선택): baby 육아 · pet 반려동물 · wedding 웨딩 · insurance 보험 · law 법률 · labor 노무 · consumer 소비자 상담(환불·청약철회 등) · region 지역 출산지원금(시·도) · brand 브랜드(GEO 광고주 제공 · 세탁·용품 팁) · etc 연말정산·레시피·나들이 등

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"분야(선택): baby 육아 · pet 반려동물 · wedding 웨딩 · insurance 보험 · law 법률 · labor 노무 · consumer 소비자 상담(환불·청약철회 등) · region 지역 출산지원금(시·도) · etc 연말정산·레시피·나들이 등"New value: +"분야(선택): baby 육아 · pet 반려동물 · wedding 웨딩 · insurance 보험 · law 법률 · labor 노무 · consumer 소비자 상담(환불·청약철회 등) · region 지역 출산지원금(시·도) · brand 브랜드(GEO 광고주 제공 · 세탁·용품 팁) · etc 연말정산·레시피·나들이 등"
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "baby",
      -  "pet",
      -  "wedding",
      -  "insurance",
      -  "law",
      -  "labor",
      -  "consumer",
      -  "region",
      -  "etc"
      -]New value: +[
      +  "baby",
      +  "pet",
      +  "wedding",
      +  "insurance",
      +  "law",
      +  "labor",
      +  "consumer",
      +  "region",
      +  "brand",
      +  "etc"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"분야(선택): baby 육아 · pet 반려동물 · wedding 웨딩 · insurance 보험 · law 법률 · labor 노무"New value: +"분야(선택): baby 육아 · pet 반려동물 · wedding 웨딩 · insurance 보험 · law 법률 · labor 노무 · consumer 소비자 상담(환불·청약철회 등) · region 지역 출산지원금(시·도) · etc 연말정산·레시피·나들이 등"
    • changedInput schema / properties / category / enum
      Previous value: -[
      -  "baby",
      -  "pet",
      -  "wedding",
      -  "insurance",
      -  "law",
      -  "labor"
      -]New value: +[
      +  "baby",
      +  "pet",
      +  "wedding",
      +  "insurance",
      +  "law",
      +  "labor",
      +  "consumer",
      +  "region",
      +  "etc"
      +]
  3. 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 readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds useful context: it returns question, short answer, and source name/address, and it warns that labor info is official-source-based and not legal advice. It says nothing about result ordering, when an empty result occurs, or how limit interacts with paging.

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 opening sentence is front-loaded and the example queries are efficient. The trailing English sentence restates the same scope already given in Korean, which is pure duplication, and the topic list appears twice in slightly different forms.

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 no output schema, the description carries the return shape (question, answer, source name and URL) and a legal-advice caveat, which is what an agent needs to trust the results. All three parameters are enum/description-covered in the schema, so the remaining gaps are minor.

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%, so the schema already documents query, category enum values, and the 1-10 limit with default 5. The description reinforces the topical mapping of categories and offers example query strings, but adds no syntax, tokenization, or matching-behavior detail beyond the schema. 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 ('베이비뉴스 Q&A를 찾는다') and enumerates the topical scope (parenting, wedding, pets, insurance, law, labor). An agent can tell it retrieves Q&A entries rather than articles or centers, but it never names a sibling such as get_qa, so the boundary with the single-item retrieval tool stays implicit.

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?

Topical coverage plus four concrete example queries ('펫보험 가입 나이', '청약철회 기간', etc.) give a clear sense of when this tool applies. There are no explicit exclusions or pointers to alternative tools for lookups that fall outside these domains.

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.