Skip to main content
Glama
syleedlabs

deal-locator-mcp

by syleedlabs

실거래 종합카드

deal_card_search
Read-onlyIdempotent

Retrieve a comprehensive deal card for a property address, showing latest sale price, average unit price, buy/sell indicators, and building register data for Seoul commercial properties.

Instructions

지번의 실거래 종합카드 1콜 — 최신 매매가·평단가·매도/매수·매칭 신뢰도 + 표제부.

서울 상업업무용 매매 한정. months(160)는 조회 기간(개월). 첫 조회는 표제부·실거래 API를 불러 수십 초수 분 걸릴 수 있다(이후 15분 캐시). 수치를 계산에 쓸 때는 텍스트가 아니라 structuredContent 를 읽을 것 (status='OK' 일 때만 latest 에 실측값이 있다).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
monthsNo
addressYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNo
queryYes
latestNo최신 매칭 거래 1건. status != 'OK' 이면 null.
sourceYes
statusYesOK 일 때만 latest 에 실측값이 있다. 그 외에는 수치를 추측·보간하지 말 것.
addressNo
messageNostatus != 'OK' 인 사유
buildingNo매칭 앵커가 된 건축물대장 표제부.
lookup_statusNo도메인 원본 상태(거래있음/거래없음/표제부없음 …)
period_monthsYes
cancelled_countNo제외된 해제신고 건수
transaction_countYes기간 내 매칭 거래 수(deal_history 로 전체 확인)
Behavior5/5

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

The description significantly supplements annotations by disclosing that the first call can take tens of seconds to minutes, data is cached for 15 minutes, and structuredContent should be used for calculations with status-dependent fields. No contradiction with annotations.

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?

The description is concise with no wasted words, front-loads the main purpose, and provides necessary details in a single paragraph. Could be slightly more structured but remains effective.

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?

Given the presence of an output schema, the description adequately covers purpose, usage, parameter range, and behavioral notes. It does not address error handling but is sufficient for the tool's complexity.

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?

With 0% schema coverage, the description explains the months parameter range (1-60) but does not elaborate on the address parameter format or other constraints. Partial compensation for missing schema descriptions.

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?

The description clearly states the tool provides a real estate comprehensive card for a land parcel number in Seoul commercial business use, listing specific outputs like transaction price, average price, sell/buy, and reliability. While purpose is specific, it does not explicitly distinguish from sibling tools like deal_card_create.

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?

The description specifies the geographic and property type limitation (Seoul commercial business only) and mentions first call may be slow with caching after 15 minutes. It does not explicitly exclude alternatives but provides clear context for when to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/syleedlabs/deal-locator-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server