Skip to main content
Glama
tae0y

Korea Real Estate MCP

by tae0y
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

get_villa_trades

Fetch row-house and multi-family (villa) sale records by region and month from Korea's real estate API.

Instructions

Return row-house and multi-family (연립다세대) sale records for a region and month.

Korean keywords: 빌라, 연립, 다세대, 연립다세대, (아파트외 중) 저층 공동주택
Notes:
  - "빌라" is not a legal housing type; it is commonly used to refer to "다세대/연립".

Items include house_type ("연립" or "다세대") for distinguishing subtypes.
Villas are typically cheaper than apartments and may suit budget-constrained buyers.

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: Trade list (unit_name, dong, house_type, area_sqm, floor,
           price_10k, trade_date, build_year, deal_type)
    summary: median/min/max price_10k, 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.6/5.0
Behavior4/5

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

No annotations exist, so the description fully handles transparency. It details return items (including error handling) and implies read-only behavior. Could mention rate limits or required permissions, but the existing detail is strong.

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?

Well-organized with clear sections (main description, keywords, notes, args, returns). Every sentence adds value. Front-loaded with main purpose. No wasted words.

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 moderate complexity and presence of an output schema, the description is exceptionally complete. It explains all parameters, return structure with fields and summary, and provides usage tips. Covers edge cases and error handling.

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 lacks parameter descriptions (0% coverage). The description compensates fully: explains region_code as a 5-digit code from get_region_code, year_month in YYYYMM with a fallback suggestion, and num_of_rows with default. Adds meaning beyond schema.

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?

Description clearly states it returns row-house and multi-family sale records for a region and month. Includes Korean keywords and distinguishes from sibling tools by specifying housing type (villa, row-house, multi-family).

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?

Provides context on when to use (budget-conscious buyers) and references sibling tools for prerequisites (get_region_code, get_current_year_month). Does not explicitly exclude alternatives but offers sufficient guidance.

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