Skip to main content
Glama
syleedlabs

deal-locator-mcp

by syleedlabs

매칭 근거

match_explain
Read-onlyIdempotent

Verify estimated matches by comparing anchor values and transaction row values. Audit matching logic before citing in reports.

Instructions

최신 매칭의 근거를 투명하게 — 표제부 앵커값 vs 거래행값, 발화 단계, 필지세트.

추정매칭 검증·감사용. 보고서 인용 전 반드시 확인 권장. structuredContent 의 comparison 이 앵커 대 거래행 대조(delta·equal)를 담는다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
monthsNo
addressYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rowNo실거래 원본 행(비교 대상).
dealNo설명 대상 거래(최신 1건).
queryYes
anchorNo표제부 앵커(비교 기준). null 이면 지번이 노출된 거래라 스펙 대조 없이 매칭된 것.
sourceYes
statusYesOK 일 때만 verdict/anchor/row 에 실측값이 있다.
addressNo
lot_setNo
messageNostatus != 'OK' 인 사유
verdictNo매칭 판정. confidence_score < 0.90 은 추정 — 공부 대조 전 확정 인용 금지.
multi_lotNotrue면 대지면적 비교를 완화해 매칭한 것
anchor_viaNo직접/부속지번/인접본번
comparisonNo앵커 vs 거래행 대조. anchor 가 없으면 null.
disclaimerNo
anchor_bunjiNo
lookup_statusNo
period_monthsYes
Behavior3/5

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

Annotations already provide readOnly, openWorld, idempotent, and non-destructive hints. The description adds that the output contains comparison data in structuredContent, which gives some behavioral context beyond annotations, but does not detail other traits like rate limits or authentication.

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?

The description is relatively concise but uses technical jargon without explanation. It front-loads the purpose but misses parameter information, making it less efficient in providing complete understanding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has an output schema and annotations, the description covers the high-level purpose and output content. However, it fails to explain the parameters, which are essential for correct invocation, leaving significant gaps.

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

Parameters1/5

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

The input schema has two parameters (months, address) with schema_description_coverage 0%. The description does not explain the meaning or usage of either parameter, forcing the agent to infer from context.

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 shows the basis of matching, comparing anchor values vs transaction row values, utterance stage, and parcel set. It is specific about what it does and mentions use for verification/audit, but does not explicitly distinguish from sibling tools like deal_card_search or deal_history.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides usage guidance by stating it is for verification/audit of estimated matching and recommends checking before citing in reports. However, it does not specify when not to use the tool or mention alternatives among siblings.

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