Skip to main content
Glama

korea-realty

by app.sallim
OverviewDiscussionsAdmin

[유료] 시장 신호 (미분양·심리지수)

realty_market_signals
Read-onlyIdempotent

[유료] 미분양 추이와 시장심리지수를 한 번에 조회한다. 매수 타이밍 판단의 거시 신호. 준공후 미분양(unsold_completed, 지역 합계)도 같은 모양으로 싣는다.

기본 창은 **6개월**이다(방향 판단에 필요한 최소). 더 긴 추이가 필요하면 months를
올리되, 전국 조회에서 창을 넓히면 오래된 달부터 예산에 맞춰 떨어지고 그 사실이
meta.truncated·meta.truncated_note에 값으로 실린다 — region을 지정하면 전 창이 온다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
monthsNo시계열 개월 수 (기본 6). 전국(region 미지정)에서 창을 넓히면 시도 18곳×월 행이 곱으로 늘어 응답이 도구 결과 한계에 걸린다 — 긴 창이 필요하면 region으로 지역을 좁혀라 (허용 범위 1~36)
regionNo지역명 (예: 서울). 비우면 전국

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / months / default
      Previous value: -12New value: +6
    • changedInput schema / properties / months / description
      Previous value: -"시계열 개월 수 (허용 범위 1~36)"New value: +"시계열 개월 수 (기본 6). 전국(region 미지정)에서 창을 넓히면 시도 18곳×월 행이 곱으로 늘어 응답이 도구 결과 한계에 걸린다 — 긴 창이 필요하면 region으로 지역을 좁혀라 (허용 범위 1~36)"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "realty_market_signalsDictOutput",
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedInput schema / properties / months / description
      Previous value: -"시계열 개월 수"New value: +"시계열 개월 수 (허용 범위 1~36)"
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower. The description earns credit by disclosing a non-obvious runtime behavior: nationwide widening drops the oldest months to fit a budget and reports this via meta.truncated and meta.truncated_note, while region-scoped queries return the full window.

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?

Front-loaded with purpose and scope, then the truncation caveat — good ordering. Slightly repetitive: the truncation/budget behavior is stated in the prose and again inside the months parameter schema, so a bit of the text does not earn its place.

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?

No output schema exists, yet the description tells the agent what comes back structurally — both the 미분양 series and 준공후 미분양(unsold_completed, regional total) in the same shape, plus the meta.truncated fields. For a 2-param read-only tool with full annotation coverage, nothing needed for correct invocation is missing.

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 baseline is 3, but the description adds rationale beyond the schema: why months defaults to 6 (minimum needed for direction judgment), the multiplicative blow-up of 18 시도 × months rows, and the region-scoping workaround. That is real added meaning over the parameter definitions.

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?

States a specific verb and resource set — 미분양 추이(unsold trend) and 시장심리지수(sentiment index) queried together — plus the downstream purpose (매수 타이밍 판단의 거시 신호). An agent can distinguish it from generic siblings like realty_macro_indicators or realty_supply_demand_balance because it names the exact two signal sources it bundles.

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?

Gives explicit context for the default window (6 months is the minimum for 방향 판단) and a conditional rule: widen months when a longer trend is needed, but narrow to a region first because nationwide widening hits the result limit. It does not name an alternative sibling for nationwide long-window queries, which keeps it from a 5.

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