Skip to main content
Glama

어린이집·유치원 채용공고 찾기

search_childcare_jobs
Read-onlyIdempotent

베이비뉴스 어린이집·유치원 채용포털의 공개 채용공고를 지역·직종(보육교사·대체교사·조리사·영양사·원장 등)·고용형태·신규 등록·마감 임박으로 찾는다. 마감 지난 공고는 빠지고, 시설·직종·지역·급여·마감일·공고 주소를 돌려준다. 질문 예: "서울 보육교사 채용", "고양시 어린이집 조리사 구인", "이번 주 새 어린이집 채용공고". Searches open job postings at Korean daycare centers and kindergartens.

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

Input Schema

NameRequiredDescriptionDefault
roleNo직종(예: 보육교사, 대체교사, 조리사, 영양사, 원장)
limitNo개수(기본 5, 최대 10)
regionNo지역(예: 서울, 경기 고양시, 마포구)
keywordNo공고 제목·시설 이름 낱말(선택)
employmentNo고용형태(예: 정규직, 기간제, 시간제)
new_within_daysNo최근 N일 안 등록(선택, 최대 60)
closing_within_daysNoN일 안 마감(선택, 최대 60)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 behavior. The description usefully adds that expired postings are excluded and lists the returned fields (시설·직종·지역·급여·마감일·공고 주소), which is real value beyond the annotations, but it says nothing about result ordering, pagination, or why a query might return nothing.

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?

Front-loaded with the core action and scope, followed by return fields and then example queries, all of which earn their place. The trailing English sentence largely duplicates the Korean first sentence, a minor redundancy.

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 7-parameter, all-optional search tool with no output schema, the definition covers scope, filters, exclusions and returned fields. Nothing critical for a correct call is missing, though ordering/default behavior of the result set is left implicit.

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 with examples and bounds, so the schema does the heavy lifting. The description restates role and region examples but adds no new semantics such as how filters combine or how new_within_days and closing_within_days interact; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('공개 채용공고를 ... 찾는다' / 'Searches open job postings at Korean daycare centers and kindergartens') and enumerates the filter dimensions (지역·직종·고용형태·신규 등록·마감 임박). It clearly separates itself from the sibling search_childcare_centers, which deals with facilities rather than job postings.

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?

Example queries ('서울 보육교사 채용', '고양시 어린이집 조리사 구인', '이번 주 새 어린이집 채용공고') give concrete usage context and implicitly map to the filter params. It lacks explicit when-not guidance or a named alternative, so it stops short of a 5.

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.