Skip to main content
Glama
korea-realestate-mcp

korea-realestate-mcp

by hall7024

전세가율

jeonse_ratio
Read-onlyIdempotent

Calculate the jeonse-to-sale price ratio for a Korean property by comparing a deposit with median sale and jeonse prices per ㎡, and optionally return estimated values and position among comparables.

Instructions

같은 조건의 ㎡당 매매 중앙값 대비 ㎡당 전세 보증금 중앙값(전세가율)을 계산합니다. deposit과 area를 주면 같은 면적의 추정 전세가·매매가와 입력 보증금의 비율, 비교 전세 중 위치도 냅니다. name·area를 주면 정확해집니다.

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>",
      "region": "<region>"
    },
    "name": "jeonse_ratio"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNo전용면적 ㎡. 예: 34평형 ≈ 84㎡, 25평형 ≈ 59㎡
nameNo단지·건물 이름 (공백 무시 부분 일치). 예: '래미안푸르지오'
monthsNo최근 몇 개월 (1~24, 기본 12)
regionYes지역. 예: '마포구 아현동', '수원시 영통구', '세종', 시군구 코드 5자리, 법정동코드 10자리
depositNo확인할 전세 보증금 (원). 예: 4억 = 400000000
propertyTypeYesapt: 아파트, rh: 연립·다세대(빌라), offi: 오피스텔

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.8/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), so the description's job is to add output and accuracy behavior — and it does: it discloses that results include estimated sale/jeonse prices for the given area, the ratio of the input deposit, and a rank among comparable jeonse transactions, plus an accuracy caveat. It stops short of describing units, sample-size dependence, or failure modes when data is thin.

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?

Three sentences, front-loaded with the calculation definition before the conditional output behavior, with no filler. The parenthetical gloss of 전세가율 is slightly redundant given the title but aids disambiguation.

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 six-parameter, two-required analytical tool with no output schema, the description supplies enough about returned values and accuracy levers to call it correctly. Remaining gaps — default window behavior, how comparisons are drawn when matches are sparse — are moderate but not blocking.

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; the description earns above that by explaining the parameter interaction rather than restating fields — the deposit+area pairing drives ratio output, and name+area is flagged as the precision-improving combination. It does not explain the role of months or the propertyType/region requirement, which the schema carries instead.

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?

The description opens with a precise verb-and-resource statement: it computes the median jeonse deposit per ㎡ divided by the median sale price per ㎡ for matching conditions. That is far more specific than the title '전세가율' alone. It does not name any sibling (market_summary, search_deals) to sharpen the boundary, so it stops short of a 5.

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?

Usage is implied through conditional phrasing — supplying deposit and area yields the ratio plus a positional comparison, and adding name·area improves accuracy. There is no explicit statement of when to pick this over market_summary or search_deals, nor any when-not-to-use guidance, so the agent must infer the selection rule.

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