Skip to main content
Glama

어린이집·유치원 찾기

search_childcare_centers
Read-onlyIdempotent

전국 어린이집·유치원(운영 중 약 3.3만 곳) 공시 자료에서 지역·이름·유형(국공립·민간·가정·직장·사립 등)·통학차량으로 찾는다. 이름·유형·주소·대표전화·정원·현원·통학차량·홈페이지와 상세 주소, 자료 기준일을 돌려준다(가나다순, 순위 아님). 질문 예: "마포구 국공립 어린이집", "고양시 덕은동 어린이집", "통학차량 있는 어린이집 강남구". Searches public disclosure data on 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_centers"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo어린이집 또는 유치원(선택)
nameNo시설 이름 일부(선택)
typeNo유형(선택: 국공립·민간·가정·직장·사회복지법인·협동·공립·사립)
limitNo개수(기본 5, 최대 10)
regionNo지역(예: 서울 마포구, 고양시 덕은동, 부산 해운대구)
school_busNo통학차량 운영하는 곳만(선택)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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. The description adds genuinely useful behavior beyond that: the result ordering is 가나다순 and explicitly not ranked (순위 아님), and a 자료 기준일 is returned. It omits any note on matching semantics (partial name match) or what happens when no facility matches, which limits it to a 3 rather than higher.

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 capability, dataset size, return fields, and sort order come first, with examples trailing; every element is relevant. The trailing English sentence partly duplicates the Korean content and the three example queries could be trimmed without loss.

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?

No output schema exists, and the description compensates well by enumerating the returned fields (이름·유형·주소·대표전화·정원·현원·통학차량·홈페이지·상세 주소·자료 기준일) and the sort order. For a fully optional-parameter search tool that is close to complete; only no-match behavior and match semantics remain undefined.

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%, so the baseline is 3. The description's type list (국공립·민간·가정·직장·사립 등) and region examples essentially restate what the schema already documents for type and region, adding no new syntax, defaults, or interaction rules (e.g., how name and region combine).

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 names a specific verb+resource (공시 자료에서 … 찾는다 / searching daycare and kindergarten disclosure data) and quantifies scope (약 3.3만 곳), plus it enumerates the queryable dimensions (지역·이름·유형·통학차량). It never names a sibling such as get_childcare_center_details or compare_childcare_centers, so the differentiation is only implicit through the list of returned summary fields.

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?

Three concrete example questions ("마포구 국공립 어린이집", "고양시 덕은동 어린이집", "통학차량 있는 어린이집 강남구") give clear context for when this tool applies. There is no explicit exclusion or pointer to the detail/compare tools, so the agent must infer when to escalate to a sibling.

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.