Skip to main content
Glama

어린이집·유치원 상세

get_childcare_center_details
Read-onlyIdempotent

어린이집·유치원 한 곳의 공시 정보: 정원·현원·교직원 수·보육실(반)·놀이터·CCTV·통학차량·운영시간·개원일·대표전화·홈페이지·상세 주소·기준일. 질문 예: "OO어린이집 정원과 통학차량". Details of one Korean daycare center or kindergarten from public disclosure data.

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": {
      "id": "<id>"
    },
    "name": "get_childcare_center_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes시설 id 또는 kids.ibabynews.com 주소 끝말·이름

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: the data provenance ('공시 정보' / public disclosure data) and the inclusion of a 기준일 (as-of date), which tells the agent results are a dated snapshot. It does not say what happens with an invalid or unknown id.

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 field inventory is front-loaded and dense, followed by a sample question and a one-line English gloss. Every element is informative, though the field list is long enough to read as an enumeration rather than a prioritized summary.

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 compensates by listing the returned disclosure fields, which is the most important missing piece. Annotations carry the safety profile for this read-only, closed-world lookup, and the single required parameter is fully documented, leaving only error behavior and id-form precedence unstated.

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 single 'id' parameter is documented as an id, a kids.ibabynews.com URL suffix, or a name. The description adds no further meaning about id resolution or precedence among those forms, so the baseline of 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 names a specific resource ('어린이집·유치원 한 곳') and enumerates the disclosure fields returned (정원, 현원, 교직원 수, CCTV, 통학차량, 주소, 기준일), so an agent knows exactly what it gets. It distinguishes itself implicitly from the search/compare siblings by emphasizing a single facility ('한 곳의 공시 정보'), but never names those alternatives explicitly.

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?

The sample question ('OO어린이집 정원과 통학차량') gives a concrete usage cue that clearly signals when to reach for this tool. There is no when-not guidance and no mention of search_childcare_centers or compare_childcare_centers as alternatives, so the agent must infer the boundary itself.

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.