Skip to main content
Glama

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

Check items against conditions

check_items
Read-only

For up to 20 items, say per condition whether it is met, not met or unknown (unknown when the needed case or building information was not read). Use this when: the person has a short list and wants each item checked against conditions. Without a subscription, conditions on sale chance or risk signals answer locked.

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

Input Schema

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

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 the safety profile (readOnlyHint true, openWorldHint false), and the description adds real value beyond them: the 20-item cap, the meaning of the 'unknown' state when case or building data was not read, and a subscription gate that locks sale-chance and risk-signal conditions. It does not explain error behavior or what happens with partial data, keeping it below 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?

Purpose and output semantics are front-loaded in the first sentence, followed by usage and gating details, with no filler. The phrasing 'say per condition whether it is met' is slightly convoluted and the subscription sentence is terse jargon, but the text is compact overall.

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?

There is no output schema, so the description carries the return-shape burden; it conveys the status vocabulary but not whether results are grouped per item or per condition. Combined with an unexplained ids/case_nos relationship and an undocumented nested conditions object, this is adequate but incomplete for a 4-parameter tool.

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 50%: ids and case_nos are bare arrays with no description, and the description never says whether they are alternatives or combined, nor how the nested conditions object relates to question beyond what the Korean schema text already states. The only added detail, 'up to 20 items', merely restates maxItems.

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 concrete operation and its output vocabulary: evaluate up to 20 items and return per-condition status of met, not met, or unknown. It also defines what 'unknown' means, so an agent can distinguish this evaluation tool from sibling search or report tools without opening the schema.

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: the person has a short list and wants each item checked against conditions' gives a clear selecting condition, implicitly steering broad discovery to search_items. It stops short of naming an explicit alternative or stating when not to use it, so it falls short of 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