Skip to main content
Glama

korea-realty

by app.sallim
OverviewDiscussionsAdmin

[유료] 단지 가격 예측 (XGBoost)

realty_predict_price
Read-onlyIdempotent

[유료] 단지의 다음 달 평균 매매가를 평형대별로 예측한다 (XGBoost v4_clean).

complex_name 또는 complex_key 중 하나는 필수. 동명 단지가 여러 지역에 있으면
먼저 realty_complex_report로 단지를 특정한 뒤 complex_key로 호출하라.
예측 지평은 1개월(익월) 고정 — 그 너머는 모델이 검증되지 않아 제공하지 않는다.
커버리지 밖은 정직하게 거절된다(지어내지 않음) — ①최근 3개월 내 월 거래 3건 미만이거나
②과거 거래 이력이 없는 신축 첫 달(모델이 지역·평형 평균을 토해 2~4배 틀린다, 실측).
예측이 없을 뿐 시세 데이터는 있으니 그때는 실거래 도구로 답하라.
응답 predictions[].caution이 있으면 반드시 함께 전달하라 — 예측 대상이 '익월에 거래된
매물들의 평균가'라, 시세가 그대로여도 거래 구성이 바뀌면 흔들린다(실측 16.3%가 ±10% 초과).
응답의 as_of_ym(기준월)·disclaimer(검증 MAPE)를 사용자 답변에 반드시 함께 전달하라 —
예측은 참고 지표이지 투자 보장이 아니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
monthsNo(구버전 호환) 예측 지평은 1개월 고정 — 이 값은 무시되고 응답이 그 사실을 실토한다 (허용 범위 1~12)
complex_keyNo정확한 단지 키 — realty_complex_report가 돌려주는 complex_key
complex_nameNo단지명 (예: 반포자이)
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
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "realty_predict_priceDictOutput",
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedInput schema / properties / months / description
      Previous value: -"(구버전 호환) 예측 지평은 1개월 고정 — 이 값은 무시되고 응답이 그 사실을 실토한다"New value: +"(구버전 호환) 예측 지평은 1개월 고정 — 이 값은 무시되고 응답이 그 사실을 실토한다 (허용 범위 1~12)"
  4. Changed2 schema fields changed
    • changedInput schema / properties / months / default
      Previous value: -6New value: +1
    • changedInput schema / properties / months / description
      Previous value: -"예측 개월 수"New value: +"(구버전 호환) 예측 지평은 1개월 고정 — 이 값은 무시되고 응답이 그 사실을 실토한다"
  5. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds substantial non-obvious behavior: a fixed 1-month horizon that ignores the months param, honest refusal outside coverage, measured error rates (2-4x off for new builds, 16.3% exceeding ±10%), and mandatory relaying of caution/as_of_ym/disclaimer. This goes well past what annotations convey.

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?

Purpose and the required-identifier rule are front-loaded, and each subsequent sentence carries a distinct operational fact (horizon limit, refusal cases, rerouting, mandatory field relaying). It is dense rather than padded, though the length is near the upper bound for a description.

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 compensates by naming the response fields an agent must surface (predictions[].caution, as_of_ym, disclaimer) and the footnotes behavior toggled by include_footnotes. Nothing needed to call or report this tool correctly appears to be 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 description coverage is 100%, so the schema already documents each field, making 3 the baseline. The description nonetheless adds what the schema cannot: an at-least-one-of complex_name/complex_key constraint (the schema shows 0 required params) and the dependency on realty_complex_report to obtain complex_key.

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+resource+scope: predicting next month's average sale price by pyeong band via a named model version. It is clearly distinguished from similar siblings like realty_complex_pyeong_price (current price) by explicitly framing the output as a forecast for 익월.

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?

Explicitly states the alternative and the condition: if multiple complexes share a name, resolve with realty_complex_report first and call with complex_key. It also defines when the tool will NOT answer (under 3 monthly transactions in 3 months, brand-new complexes with no history) and routes the agent to 실거래 도구 in that case.

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