Skip to main content
Glama

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

Search items

search_items
Read-only

List upcoming court-auction items by words or conditions, sorted by sale day, chance or discount. Use this when: someone wants a list of items to browse or page through. 구독 없이는 사건번호·법원·종류·지역·매각일·감정가·최저가·유찰·링크만, 예상 낙찰가·범위·낙찰 가능성·위험 신호는 구독해야 열립니다.

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": "search_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo
limitNo
offsetNo
questionNo찾고 싶은 물건을 말로. 예: 강남구 아파트 5억 이하 유치권 없는
conditionsNo조건 객체(목록 화면 주소의 조건과 같은 모양). question과 함께 주면 합쳐서 읽습니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, and the description adds genuinely new behavioral context: an unsubscribed caller sees only case number, court, type, region, sale date, appraised value, minimum price, bid failures and link, while expected winning price, range, probability and risk signals require a subscription. That tiering is not derivable from structured fields.

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-loads the core action and sorting in one sentence, then the usage condition, then the gating note. No filler, though the language switch mid-definition makes it slightly harder to scan.

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?

Covers purpose, browse/paging use case, sorting options and the crucial subscription gate on returned fields, with no output schema needed. Pagination semantics for limit/offset are not elaborated, which is the main remaining gap.

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?

The description mentions filtering 'by words or conditions' and enumerates the sort axes, which loosely maps to the sort/question/conditions parameters. With schema coverage only at 40%, limit, offset and the question/conditions merge behavior are left largely to the schema, so the description does not fully compensate.

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: 'List upcoming court-auction items,' plus the sortable axes (sale day, chance, discount). This clearly separates it from a single-item fetch like get_item, though no sibling is named explicitly.

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?

'Use this when: someone wants a list of items to browse or page through' gives a concrete selection condition that implies the alternative (fetching one item). It stops short of naming a sibling or stating when not to use it, so not a 5.

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