Skip to main content
Glama
Sign In

korea-realty

by app.sallim
OverviewDiscussionsAdmin

단지 평형별 전월세 시세

realty_complex_rent_by_pyeong
Read-onlyIdempotent

단지의 평형별 전세 보증금·월세 중앙값을 조회한다. 전세가율(전세÷매매)의 전세 축이다.

complex_key·complex_name 중 하나는 필수. 부분일치는 동명 단지가 섞일 수 있으니
가능하면 realty_search_complexes로 complex_key를 먼저 특정하라.
행 키 supply_pyeong은 **분양평**(전용㎡ ÷ 3.3058 ÷ 0.745 반올림) 기준이다.

Input Schema

NameRequiredDescriptionDefault
regionNo동명 단지를 가르는 지역 — 시군구나 **동**까지(예: '강동구', '방화동'). complex_ambiguous가 돌아오면 이 인자로 좁혀 다시 부르라
complex_keyNo정확한 단지 키 — realty_search_complexes가 돌려주는 complex_key
compare_saleNo같은 12개월 창의 **매매가를 함께 뽑아 전세가율·전월세 전환율·갭을 계산**한다(기본 켬). 종전엔 note가 '매매를 period_months=12로 따로 불러 나눠라'라고만 지시해 호출자가 손으로 했고, 창을 안 맞추면 전세가율이 수 %p 왜곡됐다 — 그 계산을 서버가 진다
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
    • addedInput schema / properties / region
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "동명 단지를 가르는 지역 — 시군구나 **동**까지(예: '강동구', '방화동'). complex_ambiguous가 돌아오면 이 인자로 좁혀 다시 부르라",
+  "title": "Region"
+}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "realty_complex_rent_by_pyeongDictOutput",
-  "type": "object"
-}New value: +null
  4. Changed1 schema field changed
    • addedInput schema / properties / compare_sale
      Added value: +{
+  "default": true,
+  "description": "같은 12개월 창의 **매매가를 함께 뽑아 전세가율·전월세 전환율·갭을 계산**한다(기본 켬). 종전엔 note가 '매매를 period_months=12로 따로 불러 나눠라'라고만 지시해 호출자가 손으로 했고, 창을 안 맞추면 전세가율이 수 %p 왜곡됐다 — 그 계산을 서버가 진다",
+  "title": "Compare Sale",
+  "type": "boolean"
+}
  5. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description still adds real value by disclosing that compare_sale makes the server compute jeonse ratio, conversion rate and gap over a matched 12-month window, and that footnotes toggle full derivation text.

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 short paragraphs, purpose stated first, then the key-resolution rule, then the row-key caveat. Content earns its place; the historical aside about the old note could have been trimmed but it justifies compare_sale's default.

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?

No output schema exists, and the description does name the row key and its basis, but it does not enumerate the remaining return fields (deposit/rent medians, footnotes structure). Adequate for an open-world read tool whose annotations already carry the safety profile.

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 a constraint the schema lacks — both key fields are nullable with no required list, yet one of complex_key/complex_name is mandatory — and explains the supply_pyeong row key is 분양평 via a specific formula.

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?

Opens with a specific verb and resource: median jeonse deposit / monthly rent per pyeong for a complex. The line "전세가율(전세÷매매)의 전세 축이다" implicitly marks it off from the sale-price sibling realty_complex_pyeong_price, though that sibling is never named outright.

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?

Gives a clear precondition (complex_key or complex_name is mandatory) and routes the agent to realty_search_complexes to resolve the key first, plus the region fallback when complex_ambiguous comes back. Missing only an explicit when-not / 'use the sale-price tool instead' clause.

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