Skip to main content
Glama
tae0y

Korea Real Estate MCP

by tae0y
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

get_apartment_rent

Retrieve apartment lease and monthly rent data for a Korean region and month. Combine with trade data to calculate the jeonse ratio and assess gap-investment risk.

Instructions

Return apartment lease and monthly-rent records for a region and month.

Korean keywords: 아파트

Use this alongside get_apartment_trades to compute the jeonse ratio:
  jeonse_ratio = summary.median_deposit_10k / trade summary.median_price_10k
A ratio above 70% signals high gap-investment risk.

Args:
    region_code: 5-digit legal district code (returned by get_region_code).
    year_month: Target year-month in YYYYMM format (e.g. "202501").
        Call get_current_year_month if not specified by the user.
    num_of_rows: Maximum number of records to return. Default 100.

Returns:
    total_count: Total record count from the API
    items: Rent list (unit_name, dong, area_sqm, floor,
           deposit_10k, monthly_rent_10k, contract_type,
           trade_date, build_year)
    summary: median/min/max deposit_10k, monthly_rent_avg_10k,
             jeonse_ratio_pct (null — compute from trade data),
             sample_count
    error/message: Present on API error or network failure

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
year_monthYes
num_of_rowsNo
region_codeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.7/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It details return structure including error handling and possible fields. However, it does not explicitly state that the tool is read-only or mention rate limits, which would improve transparency.

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?

Description is well-structured and front-loaded with the main purpose. It is slightly lengthy but every sentence adds value. Could be slightly more concise, but remains efficient.

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

Completeness5/5

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

Given the complexity (3 parameters, output schema exists but no nested objects), the description is very complete: covers arguments, return structure, usage with sibling tools, and error handling. No gaps remain.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must add meaning. It fully explains each parameter: region_code as a 5-digit code from get_region_code, year_month format YYYYMM with a fallback instruction, and num_of_rows with default 100.

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?

The description clearly states 'Return apartment lease and monthly-rent records for a region and month.' It also provides Korean keywords and distinguishes from siblings by referencing 'get_apartment_trades' for computing the jeonse ratio.

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 says 'Use this alongside get_apartment_trades to compute the jeonse ratio' and gives a formula. Also instructs to call 'get_current_year_month' if the user doesn't specify the year_month.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tae0y/real-estate-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server