Skip to main content
Glama

Korea Court Auction (법원 경매 예상 낙찰가)

Similar sold cases

get_sold_cases
Read-only

Past sold court-auction cases similar to one item (same kind, appraisal within half to twice, nearest area first: same 동, 시·군·구, 시·도), with sale price, sale ÷ appraisal and failed rounds. Or give a place, kind and appraisal. Use this when: the person wants comparable sales before deciding a bid. 누구나 쓸 수 있습니다.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
idNo
itemNo
kindNo
sidoNo
siguNo
courtNo
limitNo
case_noNo
questionNo물건 없이 찾을 때 지역·종류. 예: 수원시 영통구 아파트
appraisal_wonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, openWorldHint=false), and the description adds real context beyond them: the matching/ranking algorithm, the specific output fields, and '누구나 쓸 수 있습니다' signalling no authentication or ownership requirement. It does not state result-count defaults or what happens when no comparable exists, but the added value over the annotations is substantial.

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?

Dense but front-loaded: the core behavior and similarity rule come first, the alternate input mode second, and the usage trigger last. The parenthetical Korean administrative units are necessary precision, not padding; only '누구나 쓸 수 있습니다' sits slightly awkwardly at the end.

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

Completeness3/5

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

For a 10-parameter tool with no required fields and no output schema, the description explains both invocation paths and the returned fields reasonably well. However, it leaves several parameters undocumented and does not clarify how the loosely-related inputs (court, case_no, limit) interact with the primary item/place modes, which is a meaningful gap at this complexity.

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

Parameters2/5

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

Schema description coverage is only 10% across 10 parameters, so the description must carry the load and mostly does not. It explains the two input modes (one item vs. place + kind + appraisal) and implies the appraisal tolerance, but limit, court, case_no, sido/sigu spelling, and the id-vs-item distinction are never addressed.

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?

States a specific verb and resource ('Past sold court-auction cases similar to one item') and defines the similarity rule concretely: same kind, appraisal within half to twice, nearest area first with an explicit 동 → 시·군·구 → 시·도 ordering. It also names what comes back (sale price, sale ÷ appraisal, failed rounds). It does not name a sibling it is not, so differentiation from search_items or get_analysis_report is left implicit.

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 'Use this when: the person wants comparable sales before deciding a bid' clause gives a clear triggering situation rather than leaving usage implied. There is no when-not guidance and no alternative tool is named for the case where the user wants raw listings instead of comparables.

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