Skip to main content
Glama

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

Item details

get_item
Read-only

Every field of one item with Korean labels, risk flags, court photo and report links. Use this when: the person picked one item (by id or case number). Without a subscription, predicted price, band, chance and risk show as 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": "get_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
itemNo
courtNo
case_noNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description does add substantive behavior beyond that: the response includes Korean labels, risk flags, court photo and report links, and non-subscribers see predicted price, band, chance and risk as locked. However, it does not say what happens if no identifier is supplied (required parameters = 0) or whether missing fields are omitted versus null.

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?

Two tight sentences, front-loaded with what is returned followed by the selection condition. The paywall caveat is placed last where it is least disruptive. Slightly telegraphic phrasing ('with Korean labels, risk flags...') but no wasted text.

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?

For a read-only detail tool with no output schema, it adequately characterizes the return payload and the subscription gating. It falls short on the four undocumented parameters (no guidance on which identifier to use, or what to do when none is given) and says nothing about response size or missing-item behavior.

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 0% across four parameters, so the description must compensate; it only partly does. It implies 'id' and 'case_no' are alternative identifiers, but says nothing about 'item' or 'court', leaving an agent unsure which field to populate or whether they are filters or display preferences.

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 retrieval verb-resource: 'Every field of one item', and enumerates what comes back (Korean labels, risk flags, court photo, report links). This separates it from search/check style siblings by making clear it targets a single picked item, though it never explicitly frames the single-vs-list contrast.

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?

Gives an explicit trigger: 'Use this when: the person picked one item (by id or case number).' That is a clear usage condition with the identifying inputs named. It stops short of exclusions, e.g. it does not say to use search_items when the item isn't yet identified.

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