Korea Real Estate MCP

Overview Schema Source Related Servers Discussions Admin

get_apt_subscription_info

Fetch Applyhome APT subscription notice metadata to check application, winner announcement, and contract dates, plus house names and locations for Korean housing lotteries.

Instructions

Return Applyhome (청약홈) APT subscription notice metadata.

Korean keywords: 청약, 분양, 모집공고, 청약 일정, 당첨자 발표, 계약 일정

Use this tool when the user asks:
  - "청약(분양) 공고를 보고 싶어", "이번 달 모집공고 알려줘"
  - "청약 접수 시작/종료일, 당첨자 발표일이 언제야?"
  - "어떤 단지(주택명)가 분양 예정이야?"

This tool returns APT notice metadata such as notice number, house name,
location, schedule dates (announcement, application, winner, contract),
and operator/constructor information. It is not tied to region_code.

Authentication:
  - Set ODCLOUD_API_KEY (Authorization header), or
  - Set ODCLOUD_SERVICE_KEY (serviceKey query parameter).

Args:
    page: Page number (1-based).
    per_page: Items per page.
    return_type: Response type, typically "JSON".

Returns:
    total_count: Total record count from the API.
    items: Notice metadata records.
    page: Current page.
    per_page: Items per page.
    current_count: Number of returned items in this response.
    match_count: Number of matched items (may differ by API).
    error/message: Present on API/network/config failure.

Input Schema

Name	Required	Default
`page`	No
`per_page`	No
`return_type`	No	JSON

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Discloses two authentication methods and error handling. No annotations provided, so description carries the burden. Does not mention rate limits, destructive behavior (appears read-only), or performance traits.

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?

Well-structured with sections for keywords, use cases, authentication, arguments, returns. Front-loaded with purpose. Could be slightly condensed but clear and efficient.

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?

Output schema exists and description lists return fields. Covers authentication, error states, and typical usage. For a metadata list tool, it is fairly complete given the schema presence.

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 has 0% coverage, but description adds brief explanations for each parameter (1-based page, default per_page, return_type). Adds some meaning beyond schema titles and defaults but not extensive.

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?

Clearly states it returns APT subscription notice metadata. Provides Korean keywords and example user queries. Distinguishes from sibling tools like get_apt_subscription_results which handles results, not metadata.

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?

Provides concrete example questions that trigger this tool. Notes that it is not tied to region_code, implying context for when to use versus region-specific tools. Does not explicitly state when not to use or list alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server