Skip to main content
Glama

korea-realty

by app.sallim
OverviewDiscussionsAdmin

[유료] 서울 재개발·재건축 사업장

realty_redevelopment
Read-onlyIdempotent

[유료] 서울시 정비사업(재개발·재건축·가로주택) 사업장 목록을 조회한다.

[유료] 서울시 정비사업(재개발·재건축·가로주택 등) 사업장 목록 — 사업명·유형·
진행 단계·위치. "○○구 재개발 어디까지 진행됐어?"·"면목동 재개발 어디 있어?"류 질문용.
구(region)·동(dong)·유형(project_type)·진행 단계(stage)로 거를 수 있다.

**커버리지는 서울 한정**(정보몽땅 원천) — 타 시도는 이 도구로 답할 수 없다고 밝혀라.
세대수·준공예정은 원천 목록이 제공하지 않아 null이다(지어내지 말 것). 원천이 진행
단계를 비워 둔 사업장이 있다(약 2%) — stage가 빈 행은 '단계 미상'이지 '진행 없음'이 아니다.
재건축 **유망도 점수**는 이 도구가 아니라 realty_reconstruction이 담당하고,
"지금 사면 조합원 지위 승계돼?"는 realty_member_transfer_check(무료)가 담당한다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dongNo법정동 (예: 면목동·신길동) — 사업장 주소로 거른다. 구를 함께 주면 빠르다
limitNo(허용 범위 1~50)
stageNo진행 단계 필터 — plan_establishment=정비계획 수립, zone_designation=정비구역지정, safety_assessment=안전진단, committee_approval=추진위원회승인, union_establishment=조합설립인가, project_approval=사업시행인가, disposal_approval=관리처분인가, sale=분양, construction_start=착공, completion=준공인가, relocation_notice=이전고시, union_dissolution=조합해산. 비우면 전체. 원천이 단계 코드를 안 준 사업장(조합청산·조합원 모집신고 등)은 이 필터에 안 걸린다
offsetNo페이지네이션 오프셋
regionNo시군구 (예: 강남구) — 다른 도구와 같은 인자 이름. sigungu와 같은 뜻이다
sigunguNo시군구 (예: 강남구). 비우면 서울 전체. region과 같은 뜻의 옛 이름(둘 중 하나만)
project_typeNoreconstruction=재건축, housing_redevelopment=재개발(주택정비형), urban_redevelopment=재개발(도시정비형), street_housing=가로주택정비, small_reconstruction=소규모재건축, small_redevelopment=소규모재개발, regional_housing=지역주택, remodeling=리모델링. 비우면 전체

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / dong
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "법정동 (예: 면목동·신길동) — 사업장 주소로 거른다. 구를 함께 주면 빠르다",
+  "title": "Dong"
+}
    • addedInput schema / properties / region
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "시군구 (예: 강남구) — 다른 도구와 같은 인자 이름. sigungu와 같은 뜻이다",
+  "title": "Region"
+}
    • changedInput schema / properties / sigungu / description
      Previous value: -"시군구 (예: 강남구). 비우면 서울 전체"New value: +"시군구 (예: 강남구). 비우면 서울 전체. region과 같은 뜻의 옛 이름(둘 중 하나만)"
    • addedInput schema / properties / stage
      Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "plan_establishment",
+        "zone_designation",
+        "safety_assessment",
+        "committee_approval",
+        "union_establishment",
+        "project_approval",
+        "disposal_approval",
+        "sale",
+        "construction_start",
+        "completion",
+        "relocation_notice",
+        "union_dissolution"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "진행 단계 필터 — plan_establishment=정비계획 수립, zone_designation=정비구역지정, safety_assessment=안전진단, committee_approval=추진위원회승인, union_establishment=조합설립인가, project_approval=사업시행인가, disposal_approval=관리처분인가, sale=분양, construction_start=착공, completion=준공인가, relocation_notice=이전고시, union_dissolution=조합해산. 비우면 전체. 원천이 단계 코드를 안 준 사업장(조합청산·조합원 모집신고 등)은 이 필터에 안 걸린다",
+  "title": "Stage"
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "realty_redevelopmentDictOutput",
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"(허용 범위 1~50)"
  4. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, and the description goes beyond them by disclosing Seoul-only source coverage, that 세대수·준공예정 are null, and that ~2% of rows have a blank stage meaning '단계 미상' not '진행 없음'. These are genuinely useful data-quality and scope caveats. However it does not describe result ordering or how paging interactss with the filters, so it is strong-but-not-exhaustive.

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?

Front-loaded with the core capability and caveats, and mostly dense with no filler. The one inefficiency is the near-duplicate opening line ('[유료] 서울시 정비사업… 목록을 조회한다' repeated as '…목록 — 사업명·유형…'), which costs a sentence.

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?

With no output schema, the description takes on the job of describing returns (사업명·유형·진행 단계·위치) and pre-empts the obvious failure modes (fabricating null household/completion values, misreading blank stage, answering for non-Seoul regions). For a 7-param read tool with annotations already covering safety, this is complete enough to call correctly.

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

Parameters3/5

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

Schema coverage is 100% and the schema already maps every enum (stage, project_type) and alias (region/sigungu), so the description's restatement of the filterable fields adds little new meaning. Baseline 3 applies when the schema carries the parameter burden; no extra semantics or format hints are supplied.

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 and resource ('서울시 정비사업 사업장 목록을 조회한다') and enumerates the returned fields (사업명·유형·진행 단계·위치). It names the sibling it does NOT cover — realty_reconstruction for 유망도 점수 and realty_member_transfer_check for 승계 — so an agent can distinguish it without opening any schema.

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?

Gives concrete triggering questions ("○○구 재개발 어디까지 진행됐어?", "면목동 재개발 어디 있어?"), states the filter dimensions (region/dong/project_type/stage), and explicitly limits scope ('타 시도는 이 도구로 답할 수 없다고 밝혀라'). It also routes two adjacent intents to their correct tools, which is full when/when-not/alternative coverage.

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

All korea-realty toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources