Skip to main content
Glama

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

Analyze a question

get_analysis_report
Read-only

Read a person's own words about court-auction items they want (region, kind, price, risk) and answer with the matching items, what was read, what was not read, and a link to the list page. Use this when: someone describes in words which auction items they are looking for, as the first call. Without a subscription, predicted price, band, chance and risk are locked. 구독 없이도 쓸 수 있으나 예상 낙찰가·위험 신호는 구독해야 열립니다.

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": {
      "question": "<question>"
    },
    "name": "get_analysis_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYes찾고 싶은 물건을 말로. 예: 강남구 아파트 5억 이하 유치권 없는

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true and openWorldHint=false; the description adds genuinely new behavior: partial results with an explicit accounting of what was and wasn't read, plus a subscription gate that locks predicted price, band, chance and risk. That gating is exactly the kind of constraint annotations cannot express.

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

Conciseness3/5

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

The English sentences are front-loaded and earn their place, but the final Korean sentence repeats the subscription-lock information verbatim from the sentence before it, adding redundancy rather than new content.

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 read-only, single-parameter tool with no output schema, the description adequately explains input expectations, return content, and the subscription limitation on returned fields. Minor gaps remain around result volume or pagination and how unmatched criteria are reported.

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?

There is one required parameter with 100% schema description coverage, so the schema already carries the load with its own example. The description adds only that the free text may express region, kind, price and risk, which is a mild hint but largely restates the schema example rather than adding syntax or format guidance.

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 uses a specific verb+resource ('Read a person's own words about court-auction items... and answer with the matching items') and lists what comes back: matches, what was read, what was not read, and a list-page link. It does not name or contrast sibling tools such as search_items or check_items, so an agent must infer the boundary itself.

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: someone describes in words which auction items they are looking for, as the first call' gives both a trigger condition and a sequencing cue (call this first). There are no explicit exclusions or named alternatives, which keeps it below 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