법원경매 데이터 MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| auction_codesC | 법원·시도·토지/건물 대분류 코드. 하위 코드 목록 지원 범위 확인. |
| auction_searchC | 명시한 법원/지역·매각기일 범위에서 한 페이지 조회. |
| auction_detailC | 법원·사건 식별을 검증한 15A 상세. 권리분석이나 투자추천이 아님. |
| auction_collectB | 순차 수집·원자 체크포인트. 같은 job_id로 재개, 조건 변경 거부. |
| auction_job_statusC | 저장 건수·누적 요청·체크포인트·실패 요약. |
| auction_exportC | 새 로컬 폴더에 JSONL/CSV/Excel. 기존 출력은 덮어쓰지 않음. |
| auction_coverageC | 지원 기능과 실제 검증 범위·한계 확인. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct stage: search (one-page view), detail (single case), collect (bulk job), job_status (job monitoring), codes (lookup), coverage (meta/limits), export (output). The only mild overlap is auction_search vs auction_detail, but their descriptions clearly separate listing queries from case-level detail.
All seven tools share the 'auction_' prefix, giving a strong predictable pattern. Minor deviation: some use verbs (collect, export, search) while others use nouns (detail, codes, coverage, job_status), but the set remains readable and coherent.
Seven tools is well-scoped for a data collection pipeline: discovery, collection, monitoring, export, and reference lookups. Each tool earns its place with no redundant entries.
The surface covers the full workflow: codes → search → detail → collect → job_status → export, plus a coverage/limits tool. A gap exists in job management — no list_jobs to discover job_ids and no cancel/abort operation — which agents may need for recovery.