Skip to main content
Glama

korea-realty

by app.sallim
OverviewDiscussionsAdmin

[유료] 지역 비교

realty_compare_regions
Read-onlyIdempotent

[유료] 여러 지역의 매매·전세 시세와 추이를 나란히 비교한다. 갈아타기·투자처 비교용.

"어디가 제일 ○○해?"류 순위·탐색 질문은 무료 realty_region_rankings로 먼저 좁혀라 —
이 도구는 비교 대상이 정해졌을 때 쓴다.

⚠️ 지역별 `warning_baseline`·`warning_dispersion`을 avg_price보다 먼저 읽어라 —
이 소스는 이상치 미필터·단지급 혼합이라 avg_price를 그대로 "그 지역 시세"로 인용하면
특정 단지와의 비교 결론이 뒤집힌다(realty_region_price_stats와 같은 공시다).

Input Schema

NameRequiredDescriptionDefault
monthsNo추이 개월 수 (허용 범위 1~60)
regionsYes비교할 시군구 2개 이상 — 배열(['강남구','서초구']) 또는 쉼표 문자열('강남구,서초구')
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_compare_regionsDictOutput",
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedInput schema / properties / months / description
      Previous value: -"추이 개월 수"New value: +"추이 개월 수 (허용 범위 1~60)"
  4. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description still adds high-value interpretive context: warning_baseline/warning_dispersion must be read before avg_price, because the source is outlier-unfiltered and mixes complex-level data, so citing avg_price as the regional price can flip a comparison conclusion. That is exactly the kind of non-obvious caveat annotations cannot express.

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 correctly: purpose sentence, then routing rule, then caveat. Every block is load-bearing, though the warning paragraph is somewhat long and references a sibling source in a way that could be tightened.

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 partially compensates by naming return-side fields (warning_baseline, warning_dispersion, avg_price, footnotes) and their interpretation. It does not describe overall return shape or pagination, but for a comparison tool the critical interpretive guidance is present.

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% (regions format, months range 1-60, include_footnotes behavior are all documented in the schema). The description adds no syntax or format detail beyond that, so the baseline 3 applies; it does visually surface the footnotes/warning fields but not the parameters themselves.

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: it compares multiple regions' 매매·전세 시세와 추이 side by side, and adds the use case (갈아타기·투자처 비교). An agent can distinguish it from realty_region_price_stats and realty_region_rankings without opening any schema.

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 routes ranking/exploratory questions ('어디가 제일 ○○해?') to the free realty_region_rankings first and states the exact condition for using this tool instead ('비교 대상이 정해졌을 때'). This is a when/when-not/alternative rule stated outright.

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