Skip to main content
Glama

korea-realty

by app.sallim
OverviewDiscussionsAdmin

인구통계 (인구·가구·연령·인구이동)

realty_demographics
Read-onlyIdempotent

지역 인구·가구·고령화·순유입 통계를 조회한다.

지역 인구통계를 조회한다 — "인구 줄고 있어?", "1인 가구 비율은?", "고령화 심해?",
"순유입 되는 동네야?"류 질문용.

응답 meta.data_as_of가 실제 최신 시점이다 — warning이 있으면 그대로 사용자에게 전달하고,
밀린 수치를 "지금 인구"로 단정하지 말 것. 연간 계열(households·age)은 기준연도를 밝혀라.
households만 동명 시군구(중구·서구 등)를 거절한다(원천 단명 수집 결함) — 그 경우
population·migration(정식 명칭 수집)으로 대신 조회하라.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
metricYespopulation=월별 인구·세대수 / households=연별 가구원수별 가구(1인가구 등) / age=연령대(5세 구간) 분포·고령화 — 시도 단위만 / migration=월별 전입·전출·순이동
monthsNopopulation·migration 시계열 창(개월) — 최대 60(5년)이고 더 긴 창은 이 도구로 못 받는다. 연간 계열엔 미적용 (허용 범위 1~60)
regionYes시도(예: 서울)나 시군구(예: 강남구, 수원시). age는 시도 단위만 제공. age에 한해 '전국'도 가능

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "realty_demographicsDictOutput",
-  "type": "object"
-}New value: +null
  2. Changed1 schema field changed
    • changedInput schema / properties / months / description
      Previous value: -"population·migration 시계열 창(개월). 연간 계열엔 미적용"New value: +"population·migration 시계열 창(개월) — 최대 60(5년)이고 더 긴 창은 이 도구로 못 받는다. 연간 계열엔 미적용 (허용 범위 1~60)"
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, but the description adds non-obvious behavior: meta.data_as_of is the true latest timestamp, warnings must be relayed verbatim, lagged figures must not be presented as current, annual series need a stated reference year, and households has a source-data defect that rejects same-named districts.

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 (purpose, then usage questions, then behavioral caveats) and dense with useful detail, but there is mild redundancy between the opening sentence and '지역 인구통계를 조회한다'.

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?

With no output schema, the description still tells the agent what to expect back (data_as_of, warning) and how to report it, and it covers metrics scope, time-window limits, and the geographic granularity restriction for age — enough to call and interpret the tool correctly.

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% so the schema already documents metric/months/region, but the description contributes param-relevant guidance the schema lacks: the households same-name city/district rejection and the population·migration workaround, plus the annual-vs-monthly window distinction.

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 first line names a specific verb (조회한다 = retrieves) and a specific resource (지역 인구·가구·고령화·순유입 통계 = regional population/household/aging/net-inflow statistics), which cleanly separates it from price-oriented siblings like realty_region_price_stats or realty_macro_indicators.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It enumerates the exact user questions this tool answers ('인구 줄고 있어?', '1인 가구 비율은?', '고령화 심해?', '순유입 되는 동네야?'), and gives an explicit alternative path: when households rejects same-named districts, fall back to population·migration.

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

All korea-realty toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources