Skip to main content
Glama
korea-realestate-mcp

korea-realestate-mcp

by hall7024

지역 해석

resolve_region
Read-onlyIdempotent

Converts Korean region names or codes into the sigungu code and legal dong required for real-transaction price lookup, returning all candidates when names overlap and accepting pre-2026 names.

Instructions

지역 이름을 실거래가 조회용 시군구 코드와 법정동으로 바꿉니다. 이름이 겹치면 후보를 모두 돌려줍니다. 다른 도구의 region에는 결과의 'region에 넣을 값'을 그대로 쓰세요. 2026-07 행정구역 개편 전 이름도 받습니다.

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": {
      "query": "<query>"
    },
    "name": "resolve_region"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes지역. 예: '마포구 아현동', '수원시 영통구', '세종', 시군구 코드 5자리, 법정동코드 10자리

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds real behavior beyond them: ambiguous names return all candidates rather than an error or a guess, and pre-2026-07 administrative names are accepted — both are non-obvious traits that change how an agent should handle the response.

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, each carrying distinct information: what it does, ambiguity handling, downstream usage of the output, and legacy-name acceptance. Nothing is repeated from the schema and the most actionable instruction (reuse the returned value) 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?

There is no output schema, and the description covers the key return behavior (candidate list on ambiguity, the 'region에 넣을 값' field to reuse), which is what an agent needs to chain this tool. It stops short of naming the other returned fields or what an empty result looks like, a minor gap for a resolver.

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% and the single query parameter already lists example formats and code lengths, so the baseline is 3. The description adds meaning the schema does not: legacy pre-reorganization region names are valid input, which prevents the agent from rejecting or rewriting old names before calling.

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?

States a specific verb+resource pair: converting a region name into a 시군구 code and 법정동 for 실거래가 조회. It also makes the tool's role as a prerequisite resolver clear, which separates it from the analytics siblings (jeonse_ratio, market_summary, search_deals) without needing their schemas.

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?

Explicitly tells the agent how to use the result: put the returned 'region에 넣을 값' verbatim into other tools' region parameter, which implies calling this before the search tools. It does not state when not to use it (e.g. when the caller already has a code), so it falls short of full when/when-not guidance.

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