Skip to main content
Glama

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

Bid price scenarios

bid_scenarios
Read-only

For one item, show where bid amounts sit in the predicted 10-90% price band (an estimate), the deposit and the gap to the predicted price. No tax numbers. Use this when: the person is deciding how much to bid. 구독자 전용.

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": {
      "id": "<id>"
    },
    "name": "bid_scenarios"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
bidsNo원 단위 입찰가, 없으면 최저가부터 상단까지 6단계

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations cover read-only and closed-world behavior, and the description adds real context on top: the price band is flagged '(an estimate)', tax figures are explicitly excluded from output, and '구독자 전용' discloses a subscriber-only entitlement requirement. The untranslated access note is somewhat opaque, but the disclosure itself is valuable.

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?

Front-loaded with the core capability, then the usage condition, then the access restriction — no filler sentences. The mixed Korean/English fragments make it slightly choppy but not wasteful.

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?

There is no output schema, so the description carries the return-value burden, and it does list the returned elements (band position, deposit, gap) plus a negative scope (no tax). With only two parameters and one poorly documented, the main residual gap is that the id parameter is never explained.

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 50%: the bids array is documented in-schema as KRW amounts with a fallback of six steps from low to high, while id is undocumented. The description's 'For one item' and 'bid amounts' hint at the meaning of both parameters but adds no format or default detail beyond the schema.

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?

States a concrete verb and scope: for one item, show where bid amounts sit in the predicted 10-90% price band plus deposit and gap to predicted price. The resource and output content are explicit, though it never contrasts itself with siblings like get_item or get_analysis_report.

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?

Gives a clear triggering condition: 'Use this when: the person is deciding how much to bid,' which is enough to route an agent away from stats or report tools. It offers no explicit when-not or named alternative, so it stops short of full routing guidance.

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