Skip to main content
Glama

korea-realty

by app.sallim
OverviewDiscussionsAdmin

[유료] 전월세 수익률

realty_rental_yield
Read-onlyIdempotent

[유료] 시군구별 월세 수익률·평균 매매가·평균 월세를 조회한다. 수익형 투자 스크리닝용.

기본 응답은 최신 완결월 1개월치를 수익률 내림차순으로 자른 것이다 — 전체 기간·전체
지역이 아니다(truncated 필드 확인). 특정 월은 year_month로 조회하라.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo반환 행 수 — 수익률 내림차순 상위 N (허용 범위 1~50)
regionNo시도(예: 서울특별시) 또는 시군구(예: 강남구). 세종은 시 단위로 나온다
year_monthNoYYYYMM (기본 최신 완결월)
pyeong_supplyNo분양평수(예: 25·34) — 서버가 ×0.745로 전용평으로 환산해 **전용평 구간**(S·M·L·XL·XXL)을 고른다(분양 25평→S, 34평→M)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / pyeong_supply / description
      Previous value: -"분양평수 20/25/34/40/50 중"New value: +"분양평수(예: 25·34) — 서버가 ×0.745로 전용평으로 환산해 **전용평 구간**(S·M·L·XL·XXL)을 고른다(분양 25평→S, 34평→M)"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "realty_rental_yieldDictOutput",
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"반환 행 수 — 수익률 내림차순 상위 N"New value: +"반환 행 수 — 수익률 내림차순 상위 N (허용 범위 1~50)"
  4. Changed3 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 30,
+  "description": "반환 행 수 — 수익률 내림차순 상위 N",
+  "maximum": 50,
+  "minimum": 1,
+  "title": "Limit",
+  "type": "integer"
+}
    • changedInput schema / properties / region / description
      Previous value: -"시도 단위 (예: 서울특별시) — 응답은 시군구별로 온다"New value: +"시도(예: 서울특별시) 또는 시군구(예: 강남구). 세종은 시 단위로 나온다"
    • changedInput schema / properties / year_month / description
      Previous value: -"YYYYMM (기본 최신월)"New value: +"YYYYMM (기본 최신 완결월)"
  5. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare read-only/idempotent behavior, and the description adds important non-obvious behavior: results are truncated to one month and sorted descending, with a truncated field to inspect. This genuinely helps the agent avoid misinterpreting partial data.

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?

Two short paragraphs: the first states purpose and audience, the second states the critical caveat about truncation and how to override it. Every sentence earns its place and the key warning is front-loaded.

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 read-only query tool with no required parameters and a well-annotated schema, the description covers purpose, default behavior, and the main parameter to adjust. It could clarify whether a null region returns nationwide data, but the truncation warning covers the most important ambiguity.

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 coverage is 100% and parameter descriptions already explain limit, region, year_month, and pyeong_supply, including default behaviors and conversion logic. The description reinforces the sorted/truncated default but adds little beyond the schema.

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?

Description states a specific verb ('조회한다') and resource ('시군구별 월세 수익률·평균 매매가·평균 월세'), making the tool's function clear. It does not explicitly differentiate from the many realty siblings, so it falls 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives practical usage context: default returns only the latest completed month sorted by yield, not the full period or region, and directs the user to use year_month for a specific month. It does not name alternatives or exclusions, but the guidance is actionable.

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