Skip to main content
Glama

korea-realty

by app.sallim
OverviewDiscussionsAdmin

모집공고 팩트시트 — 전매제한·자격·층별 분양가·옵션가·중도금

realty_notice_facts
Read-onlyIdempotent

입주자모집공고 원문에서 추출·검증한 팩트시트를 항목별로 준다.

입주자모집공고 **원문**에서 추출·검증한 팩트시트 — 전매제한·재당첨제한·거주의무·
거주요건, 청약 일정, 층별 분양가표(대지비·건축비·회차별 납부액), 특별공급 배정,
발코니 확장·유상옵션 가격, 중도금 회차 일정, 예비입주자 규칙.

전매제한 기간, 재당첨 제한, 거주의무, 특별공급 자격·배정, 층/타입별 분양가,
발코니 확장비·유상옵션 금액, 중도금 회차와 납부일 — 이 값들을 묻는 질문이 이 도구의
자리다(추정하거나 웹에서 찾을 필요 없이 공고 원문 값이 나온다). 모든 값에 공고 쪽
번호(`p`)가 붙으니 답변에 notice_version(공고 판본)과 쪽 번호를 함께 제시하라.

팩트시트 미추출 공고는 원문 앞쪽(단지 주요정보 표) 텍스트를 unverified_source_text로
준다 — 수치 인용 시 "공고 원문 기준·미검증"을 명시하라. 상세 조항 전문(특공 소득기준,
부적격 처리 등)은 realty_notice_text로 원문 쪽을 직접 읽어라. 여기 없는 값은 지어내지 말 것.

⚠️ 큰 공고는 팩트시트 전체가 도구 결과 한계(64KiB)를 넘는다. 그때 **큰 절부터 떼어**
보내고 `meta.truncated`·`meta.omitted_sections`(절 이름·크기·되부르는 인자)에 그 사실을
적는다 — 뗀 절은 `section='분양가'`처럼 이름을 지정해 전문으로 받아라. **팩트시트에
없다고 공고에 없다고 답하지 마라**(못 봄 ≠ 없음).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordNo단지명 일부 (예: '우미린' — 공백 무관 매칭)
sectionNo팩트시트의 한 절만 전문으로 받는다 (예: '분양가', '공급'). 비우면 전체 — 다만 전체가 도구 결과 한계를 넘으면 큰 절부터 떼어 내고 뗀 절 이름을 meta.omitted_sections에 적는다. 그때 이 인자로 되받아라.
house_manage_noNo공고 관리번호 (realty_presale 응답의 house_manage_no)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / section
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "팩트시트의 한 절만 전문으로 받는다 (예: '분양가', '공급'). 비우면 전체 — 다만 전체가 도구 결과 한계를 넘으면 큰 절부터 떼어 내고 뗀 절 이름을 meta.omitted_sections에 적는다. 그때 이 인자로 되받아라.",
+  "title": "Section"
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "realty_notice_factsDictOutput",
-  "type": "object"
-}New value: +null
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly/idempotent/openWorld), and the description adds a lot beyond them: a 64KiB result cap, the meta.truncated / meta.omitted_sections signal, the re-fetch path via section='분양가', the p (page number) citation convention with notice_version, and the unverified_source_text fallback with a required disclaimer. These are exactly the operational traits the annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the value proposition and the field list, but the opening line ('입주자모집공고 원문에서 추출·검증한 팩트시트를 항목별로 준다') is then repeated almost verbatim in the bolded second paragraph, and the field list appears twice (once inline, once expanded). The truncation warning earns its space; the duplication does not.

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?

No output schema exists, so the description carries the return-shape burden and does: it tells the agent values come with page numbers, that an uncited answer set is possible (unverified_source_text), how truncation is surfaced, and how to recover omitted sections. Nothing an agent needs to interpret or re-request results is missing.

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 real meaning on top: it shows that section='분양가' retrieves one section in full and that this is also the recovery path for sections dropped by truncation, and it explains why keyword matches without regard to spaces. It does not restate the schema, but it does extend it usefully.

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 (extract/verify a fact sheet from the original 입주자모집공고) and enumerates the exact fields it returns: 전매제한, 재당첨제한, 거주의무, 층별 분양가표, 특별공급 배정, 발코니 확장·유상옵션, 중도금 회차, 예비입주자 규칙. It also names the sibling it is not (realty_notice_text for full clause text), so an agent can separate it from the other presale tools without opening schemas.

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?

Explicitly defines the question types it owns ('이 값들을 묻는 질문이 이 도구의 자리다', 추정하거나 웹에서 찾을 필요 없이), routes detailed clause text to realty_notice_text, and gives two negative rules: do not fabricate values not present, and do not infer absence in the notice from absence in the fact sheet. That is when-to-use, when-not, and alternatives all in one.

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