Skip to main content
Glama

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

Sale statistics by area

get_auction_stats
Read-only

Court-auction sale statistics from the court's sale results (residential, no shares): how many sold, the median and 10-90% range of sale price ÷ appraisal and the median number of failed rounds, for a 시·군·구, its 시·도 and the whole country (or every 시·도 when no place is given). Use this when: the person asks what share of the appraisal items usually sell for in a place. 누구나 쓸 수 있습니다.

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_auction_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
sidoNo예: 서울특별시
siguNo예: 강남구
monthsNo최근 몇 개월만
questionNo지역·종류를 말로. 예: 서울 강남구 아파트

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description usefully adds that the source is court sale results, that only residential items without shares are counted, and that results are aggregated rather than per-case. The Korean line '누구나 쓸 수 있습니다' hints at no auth requirement but is vague, and nothing is said about how the statistics are computed when samples are thin.

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?

One long but front-loaded sentence that leads with the data source and then enumerates the metrics, followed by a short when-to-use line. The heavy parenthetical nesting makes it dense, but every clause conveys scope or output information rather than filler.

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?

With no output schema, the description carries the burden of describing return values and does so precisely (sold count, median and 10-90% price ratio, median failed rounds, geographic breakdown levels). The only gaps are the behavior of the months window and the question shorthand parameter.

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 coverage is 80%, so the parameters are largely documented already, and the baseline of 3 applies. The description does add genuinely useful default semantics not in the schema: with no place given, every 시·도 is returned alongside national figures. However, it says nothing about the months window or the free-text question parameter.

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 resource (court-auction sale statistics from court sale results, residential only, excluding shares) and itemizes exactly what is computed: sold count, median and 10-90% range of sale price ÷ appraisal, and median failed rounds. It does not name any sibling tool to contrast with, so the agent must infer differentiation from scope alone.

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?

Explicit trigger is given: 'Use this when: the person asks what share of the appraisal items usually sell for in a place.' That maps a user-intent class to this tool clearly. There is no when-not guidance and no mention of an alternative such as get_sold_cases for individual case data.

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