Skip to main content
Glama

Reevl — Korean Real Estate

개별 실거래 내역

get_transactions
Read-onlyIdempotent

한 단지(또는 법정동)의 개별 거래를 최신순으로 준다 — 날짜·금액·면적·층까지. 다른 도구는 "최근 1년 102건"처럼 집계만 줘서 "가장 최근 거래가 언제 얼마"에 답할 수 없었다. "이 단지 최근 거래", "같은 평형 최근 10건", "직전 거래 대비 얼마나 올랐나"에 이 도구를 쓴다. ★아파트와 유형 전부 지원한다(kind 생략 시 아파트). ★전월세는 금액이 보증금·월세 둘이다 — price 하나로 뭉치지 말 것. 월세 0이면 순수 전세다. ★해제(취소)된 신고도 그대로 준다(canceled=true). 지우면 취소된 신고가를 확인할 방법이 없어서다 — 시세로 인용할 때는 반드시 빼고 말할 것. ★cid는 search_apartments·search_properties 응답에 들어 있다. 손으로 조립하지 말 것.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cidYes단지 식별자. 검색 응답의 cid를 그대로 쓴다
dealNo아파트만 해당. 기본 sale. rent면 전월세 실거래를 준다
kindNo기본 apt(아파트). ★_rent는 전월세라 응답 형식이 다르다
limitNo1~200, 기본 30
area_m2No전용면적(㎡)으로 거른다. ±1.5㎡ 안을 같은 평형으로 본다

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
cidYes
dealNo
kindYes
itemsYes최신순. 매매=date·price·area_m2·floor·canceled · 전월세=date·deposit·monthly·area_m2·floor
totalYes그 단지의 전체 거래 수(반환 건수가 아니다)
unitsYes축 이름 → 단위·뜻 설명. 숫자를 옮길 때 이 값을 그대로 읽는다
latestNo가장 최근 1건(해제 제외). 없으면 생략
noticeNo참고용 통계라는 고지. 투자 자문·중개가 아니다
sourceYes데이터 출처와 갱신일
returnedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

The description adds substantial behavior beyond the readOnly/idempotent/non-destructive annotations: canceled reports are included with canceled=true, rent transactions have both deposit and monthly rent, kind defaults to apt but supports all types, and results are sorted latest-first. These are critical quirks an agent would otherwise discover only from output data.

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?

Every sentence earns its place: purpose, differentiation, use cases, then high-value caveats about canceled records and rent amounts. The most important usage guidance is front-loaded, and no filler or schema repetition is present.

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 an output schema present and annotations covering safety, the description still handles the important missing context: canceled-report handling, rent price semantics, cid provenance, and the tool's unique role versus aggregate-only tools. Nothing needed for correct invocation is left ambiguous.

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 enriches parameter meaning: it names the exact search tools that supply cid, clarifies that _rent kinds change output format, and explains how to interpret rent amounts. This goes beyond what the schema alone provides.

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: gives individual transactions for a complex in latest order, listing date, amount, area, and floor. It explicitly contrasts with aggregation-only tools, so an agent can distinguish get_transactions from siblings that return summaries.

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?

Provides concrete use cases: 'most recent transactions in this complex', 'latest 10 same-plan transactions', and 'price change vs previous trade'. It also explains why other tools are unsuitable, giving both when-to-use and when-not-to-use guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources