Skip to main content
Glama
tae0y

Korea Real Estate MCP

by tae0y
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

get_single_house_rent

Retrieve lease and monthly rent records for detached and multi-unit houses (단독/다가구) in a specified Korean region and month. Includes deposit, monthly rent, area, and contract type.

Instructions

Return detached and multi-unit house (단독/다가구) lease/rent records for a region and month.

Korean keywords: 단독, 다가구, 단독/다가구, (아파트외 중) 단독/다가구

No unit name is provided. area_sqm is gross floor area (totalFloorAr).
house_type distinguishes "단독" from "다가구".

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, house_type, area_sqm,
           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), 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.3/5.0
Behavior4/5

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

With no annotations, the description carries full behavioral burden. It discloses that the tool returns records and includes error handling. It outlines the return structure (total_count, items, summary, error/message). It could mention rate limits or authorization needs, but overall is transparent.

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?

The description is well-structured with sections (Args, Returns) and front-loads the purpose. It is fairly concise but could be slightly trimmed without losing value. Overall, it earns its length.

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 tool's complexity (3 parameters, output schema), the description is complete. It covers parameters, return format, error conditions, and usage guidance. Nothing essential is missing.

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?

Despite 0% schema description coverage, the description extensively documents all three parameters: region_code as 5-digit legal district code, year_month in YYYYMM format with fallback instruction, and num_of_rows with default. This adds full meaning beyond the schema titles.

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 the tool returns detached and multi-unit house lease/rent records for a region and month. It provides specific Korean keywords and distinguishes house types, making the purpose unambiguous and distinct from siblings.

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?

The description provides guidance on when to use the tool (for a region and month) and references helper tools like get_region_code and get_current_year_month. However, it does not explicitly compare to sibling tools (e.g., get_apartment_rent, get_villa_rent) or state when not to use this tool.

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