Skip to main content
Glama
korea-realestate-mcp

korea-realestate-mcp

by hall7024

실거래 조회

search_deals
Read-onlyIdempotent

Query official Korean real-estate transaction records by region, property type, deal type, date, area, or complex name to review recent sales and rent data.

Instructions

국토교통부 실거래 원자료를 최신순으로 조회합니다. 금액은 원 단위입니다. 시세·전세가율 계산이 필요하면 market_summary, jeonse_ratio를 쓰세요.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "propertyType": "<propertyType>",
      "dealType": "<dealType>",
      "region": "<region>"
    },
    "name": "search_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo끝 계약년월 YYYYMM (기본 이번 달)
fromNo시작 계약년월 YYYYMM (months 대신, 최대 24개월)
nameNo단지·건물 이름 (공백 무시 부분 일치). 예: '래미안푸르지오'
limitNo돌려줄 건수 (기본 20, 최대 50)
monthsNo최근 몇 개월 (1~24, 기본 3)
regionYes지역. 예: '마포구 아현동', '수원시 영통구', '세종', 시군구 코드 5자리, 법정동코드 10자리
areaMaxNo최대 면적 ㎡
areaMinNo최소 면적 ㎡
dealTypeYessale 매매, rent 전월세 (apt·rh·sh·offi만)
propertyTypeYesapt 아파트, rh 연립·다세대, sh 단독·다가구, offi 오피스텔, presale 분양·입주권, commercial 상업업무용, land 토지, industrial 공장·창고
includeCancelledNo해제된 거래 포함 (기본 false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds two facts outside the annotations — results come newest-first and monetary values are in won — but says nothing about raw-data coverage, empty-result behavior, or rate/volume limits, and there is no output schema to fill that gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the purpose, then the unit note, then the alternative routing. Nothing is redundant with the name or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The schema is fully self-documenting and annotations are rich, which carries most of the burden for an 11-parameter tool. However, with no output schema the description never characterizes a returned record or how to interpret cancelled/ cancelled-excluded entries, leaving a real gap for a data-retrieval tool.

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%, so all 11 parameters, both enums, and the defaults are already documented in the schema. The description adds no parameter-level detail (e.g. how months interacts with from/to), so the baseline of 3 applies.

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?

Names a specific verb and resource (국토교통부 실거래 원자료 조회) plus a scope trait (최신순 ordering), which is enough for an agent to distinguish it from market_summary and jeonse_ratio, which it explicitly redirects to for aggregation needs.

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?

Provides explicit routing: if price-level or jeonse-ratio computation is needed, use market_summary or jeonse_ratio instead. It gives no guidance on other splits such as when to use resolve_region for region strings, and states no exclusions, so it is clear but not complete.

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