Skip to main content
Glama

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

Relax conditions

relax_conditions
Read-only

Count the items that match now and list the smallest changes that bring more items. Use this when: too few or no items match.

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": "relax_conditions"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionNo찾고 싶은 물건을 말로. 예: 강남구 아파트 5억 이하 유치권 없는
conditionsNo조건 객체(목록 화면 주소의 조건과 같은 모양). question과 함께 주면 합쳐서 읽습니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds a useful behavioral summary of the return content (a count plus ranked minimal relaxations), but with no output schema it does not say how many suggestions are returned, whether they are ordered, or that nothing is persisted.

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?

Two short sentences: the first states what happens, the second states the use case, so it is front-loaded with no filler. The phrasing "smallest changes that bring more items" is slightly compressed and would benefit from one clarifying word.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, nested-object tool with no output schema, the description covers purpose and trigger but leaves the shape of the result implicit. Since the tool's core value is the suggested relaxations, a brief note on what those suggestions look like would complete it.

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%, including inline descriptions for both the question and the nested conditions object, so the schema carries parameter meaning. The description adds no parameter guidance beyond that, which matches the baseline for fully documented schemas.

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 specific actions ("Count the items", "list the smallest changes") and a specific outcome (relaxing conditions to bring in more items), which separates it from read-oriented siblings like check_items and search_items. It is clear but slightly elliptical about what a "change" is.

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 an explicit trigger: "Use this when: too few or no items match," which implies it is a follow-up to a search that returned insufficient results. It does not name an alternative tool or state when not to use it, 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