Skip to main content
Glama

낙찰 통계(낙찰률·낙찰가율)

get_auction_stats
Read-onlyIdempotent

지역(·용도)의 월별 법원경매 통계 — 진행 건수, 낙찰 건수, 낙찰률, 감정가 대비 낙찰가율, 평균 입찰자 수(월 집계). '화성시 아파트 낙찰가율', '서울 경매 낙찰률 추이' 같은 질문에 쓴다. 지역은 시도부터(예: '경기 화성시', '서울', '전국'). Monthly court-auction sale rate and price-to-appraisal ratio by region.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "region": "<region>"
    },
    "name": "get_auction_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsNo최근 몇 개월(6~60, 기본 12)
regionYes지역. 예: '경기 화성시', '서울 강남구', '부산', '전국'
property_typeNo용도. 예: 아파트, 오피스텔, 다세대, 단독, 근린, 상가, 공장, 창고, 토지, 임야, 농지

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. Beyond that, the description adds real value by disclosing the aggregation granularity ('월별', '월 집계') and the exact metric set returned, which matters since there is no output schema.

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?

The metric list and example questions are front-loaded and the region-format rule follows logically. The trailing English sentence restates the already-given Korean content, which is mild duplication but not enough to hurt readability.

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 only 3 fully documented parameters, annotations covering the safety profile and no output schema, the description does enough: it states the aggregate scope, the returned metrics, and valid region shapes. Minor gaps remain around whether data is court-source only and how partial-month data is handled, but nothing needed to invoke it correctly is missing.

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 100%, so the schema already documents months (6–60, default 12), region examples, and property_type values. The description only adds a soft hint that region should be given from the 시도 level ('경기 화성시'), which is largely redundant with the schema's own examples; baseline 3 applies.

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 and scope ('지역(·용도)의 월별 법원경매 통계') and enumerates the concrete metrics returned (진행 건수, 낙찰 건수, 낙찰률, 낙찰가율, 평균 입찰자 수). It does not explicitly contrast itself with case-level siblings like get_case or get_sale_probability, so a reader must infer the aggregate-vs-per-case distinction from the word '월별/월 집계'.

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?

Example questions ('화성시 아파트 낙찰가율', '서울 경매 낙찰률 추이') give clear context for when this tool applies, and the region-format note steers correct invocation. There is no explicit statement of when NOT to use it or which sibling to pick for per-case or prediction needs.

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