Skip to main content
Glama

지역별 출산·육아 지원사업

get_support_programs
Read-onlyIdempotent

시·도, 시·군·구별로 받을 수 있는 출산지원금과 임신·출산·육아 지원사업(중앙·시도·시군구). 복지로(보건복지부) 공식 자료 기준, 신청 방법·복지로 링크 포함. 지역 이름은 시·도 정식 명칭(예: 서울특별시)과 시·군·구 이름. 질문 예: "마포구 출산지원금", "경기도 고양시 임신 지원사업". Korean central and local childbirth/parenting support programs by region (Bokjiro 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": {
      "sido": "<sido>"
    },
    "name": "get_support_programs"
  }
}

Input Schema

NameRequiredDescriptionDefault
sggNo시·군·구(예: 마포구, 선택)
sidoYes시·도(예: 서울특별시)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/ idempotent/ non-destructive/ closed-world, so safety is covered. The description adds genuine context beyond them: the data comes from official 복지로(보건복지부) sources and results include application method and Bokjiro links, telling the agent what to expect from a call. It still omits what happens for an unknown or unmatched region.

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?

Content is front-loaded: what the tool returns, the data source, name format, then example queries. The trailing English sentence is a near-verbatim translation of the Korean text and earns little for an otherwise Korean-language tool, though it aids non-Korean readers.

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 only two parameters, one required, full schema coverage, and rich annotations, the definition supplies the missing pieces an agent needs: data provenance, result contents (application method, links), and naming conventions. Return shape is described only in summary form, which is acceptable given there is no output schema but leaves field-level expectations 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 description coverage is 100%, so baseline is 3; the schema already gives the 서울특별시 and 마포구 examples that the description repeats. The only mild addition is stating that region names should use official full 시·도 designations paired with a 시·군·구 name, which reinforces format expectations rather than adding new semantics for the optional sgg parameter.

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?

Names a specific resource (출산지원금·임신·출산·육아 지원사업) with explicit scope by 시·도/시·군·구 and an official data source (복지로/보건복지부). An agent can tell this is a regional lookup of support programs, though the description never distinguishes it from nearby siblings such as plan_birth_support or list_regions.

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?

Example questions ('마포구 출산지원금', '경기도 고양시 임신 지원사업') imply the triggering use case, which is helpful. But there is no explicit when-not guidance, no routing to alternatives (e.g. list_regions for valid region names, plan_birth_support for planning), and no stated prerequisite for supplying a valid 시·도.

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.