Skip to main content
Glama

분양가 적정성 분석 — 분양가 vs 주변 실거래 시세

realty_presale_vs_market
Read-onlyIdempotent

청약(분양) 공고의 분양가가 주변 실거래 시세 대비 싼지/비싼지를 주택형별로 계산한다. "이 청약 넣을 만해?", "분양가 적정해?"류 질문의 정량 근거 — 웹검색으로는 못 하는 분양가×실거래 조인 계산이 이 도구의 존재 이유다.

공고 특정: house_manage_no가 없으면 region+keyword로 검색하고, 여러 건이면
후보 목록을 돌려주니 하나를 골라 다시 호출하라(추측해서 고르지 않는다).
기준선: 평형 행의 gap_pct는 gap_basis가 말하는 기준 대비다 — 인근 비교단지가 충분하면
**공고 좌표 반경·준공 연도 조건·같은 평형대 비교군**(nearby_baseline) 대비이고, 아니면
지역(공고 시군구, 없으면 시도) 실거래 평균(구축·외곽 포함, 이상치 미필터) 대비다. 지역 평균 대비 값은
gap_pct_region_avg에 늘 따로 있고, 두 기준선이 크게 갈리면 baseline_divergence가
붙는다 — 그때 지역 평균 대비 수치로 '비싸다'를 말하지 마라. 청약 경쟁률·당첨 가점
커트라인은 realty_subscription_odds에 있다("넣을 만해?"엔 둘을 같이 써라).
지역 수준 교차확인은 realty_area_price_bands(이상치 필터·중앙값)로 하라.
이 도구는 **현재 공고 1건의 적정성**이다 — 같은 지역 공고들의 분양가 시계열
("기다릴수록 얼마씩 올랐나")은 realty_presale_price_trend.

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_presale_vs_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsNo실거래 비교 창(개월) (허용 범위 3~24)
pyeongNo대조할 전용평(정수)을 직접 고른다 — 예: [26]이면 국민평형 84㎡만. 안 주면 **세대수 많은 순 상위 5개** 평형을 자동으로 고른다. comparison_truncated에 빠졌다고 적힌 평형은 이 인자로 되받아 부르면 된다(공시만 하고 길이 없으면 막다른 골목이다)
regionNo시도 (예: 서울, 경기, 세종)
keywordNo단지명·주소 부분일치 (예: '우미린', '5-2생활권', '다솜동')
house_manage_noNorealty_presale 응답의 공고 관리번호 — 알면 이걸로 특정하는 게 정확
include_footnotesNotrue면 계산값 근거 전문(산식·모집단·기간·원천)을 footnotes에 싣는다. 기본은 행마다 한 줄 요지
include_price_trendNotrue면 같은 지역(공고의 시도·시군구) 분양 공고들의 **연도별 평당 분양가 추이**(realty_presale_price_trend와 같은 값)를 `price_trend`에 함께 싣는다 — '지금 넣을까, 기다릴까'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / include_price_trend
      Added value: +{
      +  "default": false,
      +  "description": "true면 같은 지역(공고의 시도·시군구) 분양 공고들의 **연도별 평당 분양가 추이**(realty_presale_price_trend와 같은 값)를 `price_trend`에 함께 싣는다 — '지금 넣을까, 기다릴까'",
      +  "title": "Include Price Trend",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / include_footnotes
      Added value: +{
      +  "default": false,
      +  "description": "true면 계산값 근거 전문(산식·모집단·기간·원천)을 footnotes에 싣는다. 기본은 행마다 한 줄 요지",
      +  "title": "Include Footnotes",
      +  "type": "boolean"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / pyeong
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "integer"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "대조할 전용평(정수)을 직접 고른다 — 예: [26]이면 국민평형 84㎡만. 안 주면 **세대수 많은 순 상위 5개** 평형을 자동으로 고른다. comparison_truncated에 빠졌다고 적힌 평형은 이 인자로 되받아 부르면 된다(공시만 하고 길이 없으면 막다른 골목이다)",
      +  "title": "Pyeong"
      +}
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "realty_presale_vs_marketDictOutput",
      -  "type": "object"
      -}New value: +null
  5. Changed1 schema field changed
    • changedInput schema / properties / months / description
      Previous value: -"실거래 비교 창(개월)"New value: +"실거래 비교 창(개월) (허용 범위 3~24)"
  6. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description adds substantive beyond-schema behavior: which baseline gap_pct uses (nearby_baseline vs regional average), that regional average is always separately in gap_pct_region_avg, that baseline_divergence flags a large split, and an explicit prohibition on calling something 'expensive' off the regional average when the baselines diverge. It also discloses the candidate-list / multi-call interaction and the truncation behavior.

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 purpose, then pivots to notice identification, baseline semantics, and sibling routing in a logical order. It is dense and every section is load-bearing, though a few meta phrasings ('this is the tool's reason for existing', 'a dead end otherwise') could be trimmed without losing meaning.

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?

For a 7-parameter, zero-required tool with no output schema, the description names the key returned fields (gap_pct, gap_pct_region_avg, baseline_divergence, price_trend, comparison_truncated, footnotes) and explains the two-baseline logic an agent must not misreport. It stops short of a full return-shape description, but the critical interpretation rules are present.

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 baseline is 3, but the description adds real meaning: it explains the region+keyword fallback ordering, that house_manage_no is the most precise identifier, and that pyeong defaults to the top 5 by household count and can be used to re-fetch types dropped into comparison_truncated. That is operational semantics the schema alone does not convey.

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 computation: comparing a presale notice's price against nearby actual transaction prices, per housing type, and frames it as a quantitative answer to 'is this presale worth applying to'. It explicitly carves out boundaries against realty_subscription_odds (competition rate), realty_area_price_bands (regional cross-check) and realty_presale_price_trend (time series), so an agent can distinguish it without opening schemas.

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?

Gives an explicit decision procedure: if house_manage_no is absent, search by region+keyword, and if multiple notices come back, pick one from the candidate list and re-call rather than guessing. It also routes adjacent questions — 'should I apply' to realty_subscription_odds, regional verification to realty_area_price_bands, and 'wait or buy now' trends to realty_presale_price_trend.

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.