Skip to main content
Glama

예상낙찰가 안내

estimate_bid
Read-onlyIdempotent

경매 물건의 예상낙찰가·입찰가를 물을 때 부른다. 현재 예상낙찰가 숫자는 경매레이더 유료회원 전용이라 감정가·최저가·최저가율·유찰·매각기일과 상세 링크를 돌려준다(locked=true). 숫자를 추정해 만들지 말 것.

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": {
      "case_no": "<case_no>"
    },
    "name": "estimate_bid"
  }
}

Input Schema

NameRequiredDescriptionDefault
courtNo법원명
case_noYes사건번호. 예: '2026타경12345'
item_noNo물건번호

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses the critical behavioral fact that the actual figure is paid-member gated and that the response returns surrogate fields with locked=true. Since there is no output schema, this disclosure is what lets the agent set expectations and avoid inventing a number.

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?

Three short sentences: trigger, expected return with the gating caveat, then a guardrail against fabrication. Nothing is redundant and the most decision-relevant information (locked=true) is placed before the guardrail.

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, three-parameter tool with no output schema, the description covers the trigger, the entitlement limitation, the returned fields, and the anti-hallucination rule. The only remaining gap is that no alternative tool is named for cases where the user needs the actual numeric price.

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% (court, case_no, item_no all documented, including a case-number example), so the schema already carries parameter meaning. The description adds no parameter-level detail such as whether court/item_no are required for a unique match, so the baseline of 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 question type ('경매 물건의 예상낙찰가·입찰가') and states exactly what the tool returns instead of the number (감정가·최저가·최저가율·유찰·매각기일·상세 링크). It is clearly distinguishable from a generic case lookup, though it does not name any sibling tool as an explicit alternative.

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?

The opening sentence gives a clear trigger condition ('예상낙찰가·입찰가를 물을 때 부른다'), and the closing line adds a negative instruction not to fabricate an estimate. There are no explicit exclusions or named alternatives, so it stops short of a full when/when-not routing guide.

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