Skip to main content
Glama

법원 경매 사건 조회

court_auction
Read-only

Look up a Korean court auction case by case number and court. 법원 경매 사건번호와 법원(이름·코드)으로 사건 기본정보·매각기일·감정평가액·최저매각가격·진행상태를 조회합니다. 사건이 없으면 오류가 아니라 result 0·count 0 으로 응답하며, 정상 조회로 과금됩니다. [호출당 60포인트]

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>",
      "court": "<court>"
    },
    "name": "court_auction"
  }
}

Input Schema

NameRequiredDescriptionDefault
courtYes법원 이름 또는 법원 코드 (예: 서울중앙지방법원)
case_noYes사건번호 (예: 2024타경12345) — 연도·사건부호·번호

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already state readOnlyHint and openWorldHint, and the description adds genuinely new behavior: a missing case returns result 0/count 0 rather than an error, and the call is still billed as a normal lookup. The per-call cost (60 points) is also disclosed, which matters for an agent deciding whether to retry.

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 English sentence is front-loaded and the Korean sentence is not pure duplication — it carries the returned-field list, the not-found rule, and the billing note. Slight redundancy between the two language renderings, but nothing that fails to earn its place.

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

Completeness5/5

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

For a two-parameter read tool with no output schema, the description covers the return fields, the empty-result semantics, and the cost. An agent has everything needed to call it correctly and interpret a zero-result response.

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 both parameters (court name/code, case number with year·사건부호·번호) are already documented in the schema. The description repeats the keys without adding format or edge-case semantics beyond what the schema states.

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 names a specific verb and resource ('Look up a Korean court auction case') and scopes it by case number and court, then enumerates what is returned (기본정보·매각기일·감정평가액·최저매각가격·진행상태). No sibling in the list performs court-auction lookups, so the absence of an explicit 'not this tool' clause is not a real ambiguity.

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?

Usage is implied by the required lookup keys (case number + court name/code), but there is no explicit guidance on when to prefer this tool or what to do when the court or case number format is uncertain. The not-found rule is behavioral rather than selection guidance.

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.