Skip to main content
Glama

경매 사건 요약

get_case
Read-onlyIdempotent

경매 사건번호(예: 2026타경12345)로 물건 요약을 가져온다 — 법원·주소·용도·면적·감정가·최저가·유찰·매각기일·진행 상태·권리 표시와 위험 표시(경매레이더 판정 — 유치권·법정지상권·지분·대항력·재매각·맹지 기재)·법원 감정평가서 요항표(위치·교통·이용상태·도로·토지이용계획 등)·상세 링크. 같은 사건번호가 여러 법원에 있거나 물건이 여럿이면 후보 목록을 돌려주니 court·item_no 로 다시 부른다. '얼마 써야 하나'·예상낙찰가·입찰가 질문이 함께 있으면 estimate_bid 도 부르고, 금액을 스스로 추정하지 않는다.

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_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
courtNo법원명. 예: '서울중앙지방법원', '성남지원', '수원'
case_noYes사건번호. 예: '2026타경12345'
item_noNo물건번호(한 사건에 물건이 여럿일 때)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds a genuinely non-obvious behavioral trait beyond those annotations: the call may return a candidate list rather than a single summary, requiring a follow-up call with court·item_no. It does not discuss error/empty-result behavior, which keeps it off a 5.

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?

Front-loaded with the verb and the key identifier, followed by the fallback path and cross-tool routing — the right order. The long dash-delimited field enumeration is dense and slightly run-on, but it earns its space because there is no output schema.

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, the inline inventory of returned fields is necessary and is supplied; disambiguation and cross-tool escalation are also covered. Minor gaps remain around no-match behavior and how large the candidate list can be, but nothing critical for calling it correctly is missing.

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 all three parameters are documented, and the baseline would be 3. The description earns above baseline by giving court and item_no operational meaning as disambiguators used on the re-call, not just as optional fields, and by fixing the case_no format with a concrete example.

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?

The description names a specific verb (가져온다) and resource (물건 요약) keyed to an explicit identifier format (예: 2026타경12345), then enumerates the returned fields (법원·주소·용도·면적·감정가·최저가·유찰·매각기일·진행 상태·권리/위험 표시·감정평가서 요항표·상세 링크). An agent can tell this apart from search_auctions or estimate_bid purely from the text.

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?

It states the exact recovery path when the call is ambiguous (같은 사건번호가 여러 법원에 있거나 물건이 여럿이면 후보 목록을 돌려주니 court·item_no 로 다시 부른다) and routes bid-price questions to estimate_bid with an explicit prohibition (금액을 스스로 추정하지 않는다). Both a when-to-use and a when-to-switch are given.

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