Skip to main content
Glama

회차별 매각 확률

get_sale_probability
Read-onlyIdempotent

신건·1회 유찰·2회 유찰… 단계별로 그 회차에 매각될 확률(과거 통계). 사건번호를 주면 그 물건의 지금 단계 확률과 같은 시군구 표를, 지역·용도를 주면 시도 표를 돌려준다. '이번에 팔릴까', '한 번 더 유찰될까' 같은 질문에 쓴다. 결과를 보장하지 않는 과거 통계다.

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

Input Schema

NameRequiredDescriptionDefault
courtNo법원명
regionNo사건번호가 없을 때 지역. 예: '경기', '경기 화성시'
case_noNo사건번호(있으면 우선)
item_noNo물건번호
property_typeNo용도. 예: 아파트, 다세대, 단독, 토지, 근린, 공장

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still contributes the important caveat that these are past statistics with no guarantee of outcome, and discloses that the return shape branches depending on which inputs are supplied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences in a clean order: what the metric is, how inputs change the response, which questions it answers, and the reliability caveat. Nothing is repeated from the schema or annotations and no sentence is superfluous.

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?

For a five-parameter, all-optional read tool with no output schema, the description covers the branching logic, the intended use, and the statistical caveat. The remaining gap is that the columns/contents of the two returned tables are not described, which an agent would only learn at call time.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning the schema lacks: case_no drives the per-property plus same-sigungu table path, while region/property_type drive the sido-level table path. Only 'court' is left without any description-level explanation beyond the schema label.

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 metric — the per-round probability of sale at each stage (new filing, one failed auction, two failed auctions, etc.) — and explicitly frames it as historical statistics. It is clearly a probability-lookup tool rather than a stats aggregator like get_auction_stats or an estimate like estimate_bid, though it never names a sibling to contrast with.

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?

It gives concrete user questions that select this tool ('이번에 팔릴까', '한 번 더 유찰될까') and states the two input modes: case number for a specific property, region plus property type for the regional table. That is solid when-to-use guidance with no explicit when-not-to-use or named alternative.

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