Skip to main content
Glama

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

realty_market_signals
Read-onlyIdempotent

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

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "realty_market_signals"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsNo시계열 개월 수 (기본 6). 전국(region 미지정)에서 창을 넓히면 시도 18곳×월 행이 곱으로 늘어 응답이 도구 결과 한계에 걸린다 — 긴 창이 필요하면 region으로 지역을 좁혀라 (허용 범위 1~36)
regionNo지역명 (예: 서울). 비우면 전국
sigunguNo시군구명 (예: 창원시·수원시·중구). 주면 그 시군구의 미분양 추이를 unsold_sigungu에 **따로** 싣는다 — 시도 배열(unsold)과 합산하지 마라(이중계상). 같은 이름이 여러 시도에 있으면(중구·동구 등) region으로 시도를 함께 줘라. 심리지수·준공후 미분양은 시도 단위라 시군구로 안 좁혀진다
include_footnotesNotrue면 계산값 근거 전문(산식·모집단·기간·원천)을 footnotes에 싣는다. 기본은 행마다 한 줄 요지

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / include_footnotes
      Added value: +{
      +  "default": false,
      +  "description": "true면 계산값 근거 전문(산식·모집단·기간·원천)을 footnotes에 싣는다. 기본은 행마다 한 줄 요지",
      +  "title": "Include Footnotes",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / sigungu
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "시군구명 (예: 창원시·수원시·중구). 주면 그 시군구의 미분양 추이를 unsold_sigungu에 **따로** 싣는다 — 시도 배열(unsold)과 합산하지 마라(이중계상). 같은 이름이 여러 시도에 있으면(중구·동구 등) region으로 시도를 함께 줘라. 심리지수·준공후 미분양은 시도 단위라 시군구로 안 좁혀진다",
      +  "title": "Sigungu"
      +}
  3. 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)"
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "realty_market_signalsDictOutput",
      -  "type": "object"
      -}New value: +null
  5. Changed1 schema field changed
    • changedInput schema / properties / months / description
      Previous value: -"시계열 개월 수"New value: +"시계열 개월 수 (허용 범위 1~36)"
  6. First observed

TDQS

A3.7/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, openWorld), and the description adds real behavioral content beyond them: the default 6-month window, that nationwide windows drop oldest months and surface this in meta.truncated / meta.truncated_note, and that region restores the full window. It does not mention the '유료' (paid) cost/auth implications flagged only in the title.

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 the combined purpose, then layered detail on output keys and windowing. Sentences are dense but each covers distinct information (response keys, window default, truncation semantics); no filler.

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 no output schema, the description carries responsibility for return shape and does so partially by naming the unsold_completed and unsold_sigungu keys and the meta.truncated fields. It stops short of describing the sentiment-index output structure, but the annotations and 100% schema coverage cover the rest.

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% and the schema already documents months (including the truncation caveat and 1-36 range), region, sigungu, and include_footnotes. The description largely restates the schema's own param behavior (default window, sigungu separate key), so it adds only marginal value over structured fields.

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?

States specific verbs and resources: querying unsold-inventory trends (미분양) and the market sentiment index together, framed as a macro buy-timing signal. The scope is concrete enough to distinguish it from pure price tools, but it never names a sibling (e.g. realty_macro_indicators or realty_supply_demand_balance) that an agent might confuse it with.

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?

Implies usage via '매수 타이밍 판단의 거시 신호' and explains the months/region window tradeoff, which is useful operational guidance. However there is no explicit when-to-use versus alternatives, and no statement of when another tool would be preferable.

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.