Skip to main content
Glama

낙찰 사례

get_sold_cases
Read-onlyIdempotent

경매 사건번호를 주면 같은 동네·같은 급 물건이 실제로 얼마에 낙찰됐는지(낙찰일·감정가·낙찰가·감정가 대비 낙찰가율·유찰 횟수)를 주변 사례와 유사 사례로 돌려준다. 지난 결과일 뿐 이 물건의 예상낙찰가가 아니다 — 비율을 이 물건 감정가·최저가에 곱해 낙찰 예상 금액이나 '몇 억~몇 억 사이' 같은 범위를 말하지 말 것(예상낙찰가는 estimate_bid 유료 안내). Recent comparable court-auction sale results near a case.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "case_no": "<case_no>"
    },
    "name": "get_sold_cases"
  }
}

Input Schema

NameRequiredDescriptionDefault
courtNo법원명
case_noYes사건번호. 예: '2025타경1129'
item_noNo물건번호

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so safety is covered; the description adds value by disclosing the returned fields and the key behavioral caveat that results are historical comparables. It does not discuss data recency, court/coverage scope, or what happens when no comparables exist.

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?

Purpose and the returned fields are front-loaded, followed by the misuse warning, which is load-bearing rather than filler. The middle clause about multiplying ratios into an expected price is somewhat long-winded but earns its place as a guardrail.

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?

With no output schema and three parameters, the description carries the return-value burden, and it does list the concrete result fields. Remaining gaps are what '주변 사례' vs '유사 사례' grouping means and how results are ordered or limited, which matter for interpretation.

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 description coverage is 100%, so court, case_no, and item_no are already documented (with an example value for case_no). The description only echoes that a case number is the entry point and implies court/locality scoping; it adds no new syntax or default behavior beyond the schema. Baseline 3 applies.

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 exact fields returned (낙찰일·감정가·낙찰가·비율·유찰 횟수). It also separates itself from estimate_bid by name, so an agent can pick between them without opening a 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 explicit when-not guidance: these are past results, not a prediction for this property, and ratio-multiplying to produce an expected price is forbidden. It names the alternative (estimate_bid, paid) for expected bid, which is exactly the routing an agent needs.

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