Skip to main content
Glama
korea-realestate-mcp

korea-realestate-mcp

by hall7024

매매 시세 요약

market_summary
Read-onlyIdempotent

Summarize actual sale prices for apartments, row houses, or officetels by region, with median, range, price per ㎡, monthly trends, and recent transactions.

Instructions

매매 실거래로 시세를 요약합니다: 중앙값, 범위, 사분위, ㎡당 가격, 월별 추이, 최근 거래. name·area를 주면 범위가 좁아져 정확해지고, 여러 단지에 맞으면 후보를 돌려줍니다. 해제·직거래는 기본으로 뺍니다. 구가 여러 개인 시 전체는 호출 한도를 넘을 수 있습니다.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "propertyType": "<propertyType>",
      "region": "<region>"
    },
    "name": "market_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNo전용면적 ㎡. 예: 34평형 ≈ 84㎡, 25평형 ≈ 59㎡
nameNo단지·건물 이름 (공백 무시 부분 일치). 예: '래미안푸르지오'
monthsNo최근 몇 개월 (1~24, 기본 12)
regionYes지역. 예: '마포구 아현동', '수원시 영통구', '세종', 시군구 코드 5자리, 법정동코드 10자리
propertyTypeYesapt: 아파트, rh: 연립·다세대(빌라), offi: 오피스텔
includeDirectNo직거래 포함 (기본 false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the bar is lower, yet the description still adds real behavior: cancelled and direct transactions are excluded by default, ambiguous name matches return candidate lists instead of an error, and broad regions risk a call-limit failure. It does not cover pagination or empty-result behavior, which keeps it from the top score.

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?

Four short sentences, front-loaded with what is returned, then filter behavior, then defaults, then a limit warning. Every sentence carries distinct information with no repetition of the schema.

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 6-parameter tool with no output schema, the description enumerates the returned metrics, the default exclusions, the ambiguity path, and the scale limitation, which is enough to call it correctly. Only edge cases like zero results or result-set bounds remain unstated.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: name and area act as mutually reinforcing narrowing filters, and a name matching multiple complexes yields candidates rather than a single match. The default exclusion of direct deals also clarifies the includeDirect flag beyond its schema note.

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?

States a specific verb and resource ('매매 실거래로 시세를 요약합니다') and enumerates the exact statistics produced (median, range, quartiles, price per ㎡, monthly trend, recent deals), so an agent knows precisely what comes back. It does not name or contrast with siblings such as search_deals or jeonse_ratio, so differentiation is inferred from the output shape rather than stated.

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 concrete context for use: supplying name and area narrows the result and improves accuracy, ambiguous names return candidates, and querying a whole multi-district city may exceed the call limit. It stops short of explicit exclusions or naming the alternative tool for raw deal lookup.

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