Skip to main content
Glama

주택수요 실적 지수

get_housing_demand
Read-onlyIdempotent

시군구·시도·전국의 주택수요 실적을 연도별(20082025, 12월 말)로 돌려준다 — 인구·세대·평균 세대원·3049세 인구·연령 가중 수요(2015=100 지수 포함)와 전년 대비 증가율, 기간 변화 요약. 지역의 주택수요가 늘었는지 줄었는지, 세대 분화(1~2인 세대 증가) 정도를 물을 때 쓴다. 지난 실적만 주며 앞으로의 전망·등급은 주지 않는다(추정 금지). 읍면동 단위 자료는 없다. Korean regional housing-demand history (population, households, age-weighted demand).

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": {
      "region": "<region>"
    },
    "name": "get_housing_demand"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionYes지역. 예: '서울 강남구', '경기 화성시', '경북 의성군', '경기', '전국'. 이름이 겹치는 구(중구·남구 등)는 시도를 붙인다
to_yearNo끝 연도(기본 2025)
from_yearNo시작 연도(기본 2008)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 behavior, so safety is covered. The description adds real behavioral context beyond them: results are historical actuals only ('추정 금지'), the granularity floor is 시군구 (no 읍면동), and each year is a December year-end snapshot. It does not discuss pagination or row limits, which is a minor omission for a multi-year time series.

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 with what is returned, then when to use it, then the exclusions — a sensible order with no filler. The trailing English gloss is redundant for a bilingual model but is short and harmless.

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

Completeness5/5

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

There is no output schema, yet the description fully compensates by listing the returned fields, the index base year (2015=100), the YoY growth rate, and the period-change summary. Combined with the stated data vintage and granularity limits, an agent has everything needed to call this correctly and interpret results.

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 schema already documents all three parameters, including the ambiguous-district naming convention ('중구·남구 등은 시도 붙임') and the 2008–2025 bounds. The description adds only marginal meaning, mainly confirming the region hierarchy (시군구/시도/전국) and the year span, so the baseline 3 applies.

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?

The description names a specific verb and resource ('주택수요 실적을 연도별로 돌려준다') and pins down the exact scope: 시군구/시도/전국 levels, 2008–2025, year-end December. It also enumerates the metrics returned (인구, 세대, 평균 세대원, 30~49세 인구, 연령 가중 수요 지수), so an agent knows precisely what the tool produces before opening the schema.

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?

It gives a clear when-to-use trigger ('지역의 주택수요가 늘었는지 줄었는지, 세대 분화 정도를 물을 때') plus explicit exclusions: no forecasts or grades, no 읍면동-level data. What is missing is a named alternative for those excluded needs, but the sibling set (get_case, estimate_bid, ping, search_auctions) offers no obvious substitute, so the practical gap is small.

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.

Resources