Skip to main content
Glama

어린이집·유치원 비교

compare_childcare_centers
Read-onlyIdempotent

어린이집·유치원 2~5곳의 공시 정보(정원·현원·교직원·보육실·놀이터·CCTV·통학차량·운영시간)를 같은 칸으로 나란히 보여 준다. 우열·추천이 아닌 공개 정보 비교. 질문 예: "이 어린이집 세 곳 비교". Side-by-side comparison of 2 to 5 Korean childcare facilities.

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": {
      "ids": "<ids>"
    },
    "name": "compare_childcare_centers"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes시설 id 또는 kids 주소 끝말 2~5개

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/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 contributes the genuinely useful framing that output is disclosure data and not a ranking or recommendation, and it enumerates the compared fields – effectively describing the result columns in the absence of an output schema.

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

Conciseness5/5

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

Two sentences plus one example, front-loaded with what is compared and bounded by 2–5. The English line is a compact restatement for non-Korean readers and does not introduce bloat. Nothing here is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only comparison tool with one fully documented parameter, the definition is nearly complete, and the field list substitutes for a missing output schema. It does not say what happens when an id is invalid or how missing disclosure fields are represented, which an agent would want before calling with five ids.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single ids parameter is already documented as accepting facility ids or 'kids' address suffixes. The description reinforces the 2–5 cardinality, which matches minItems/maxItems in the schema. With one well-documented parameter there is little left to add.

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: presenting public disclosure data for 2–5 childcare facilities side by side, with the compared fields enumerated (정원·현원·교직원·보육실·놀이터·CCTV·통학차량·운영시간). An agent can tell immediately that this is a multi-facility comparison rather than a single lookup, though it never names the single-facility sibling it differs from.

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?

The example question ("이 어린이집 세 곳 비교") and the 2–5 facility bound imply the use case, and '우열·추천이 아닌 공개 정보 비교' sets an expectation. There is no explicit when-not-to-use guidance and no naming of alternatives such as get_childcare_center_details for one facility, so routing is left to inference.

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.