Skip to main content
Glama

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

Manage saved interest conditions

manage_interest
Destructive

List, add or remove the subscriber's saved interest conditions (the ones behind the mail alerts). Use this when: the person wants to save, see or delete what they follow. 구독자 전용.

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": {
      "action": "<action>"
    },
    "name": "manage_interest"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoremove할 조건 id
actionYes
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 destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered structurally. The description adds the auth constraint "구독자 전용" (subscriber-only), which is real context beyond annotations, but it never says that the remove action is the destructive/irreversible one or what adding a duplicate condition does.

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 front-loaded sentences plus a short access constraint; the action verbs come first and the usage trigger second. The trailing "구독자 전용" fragment is terse but does carry real information, so nothing is wasteful, though the language mixing in a single definition is slightly jarring.

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 mutation tool with a destructive branch, no output schema, and a nested conditions object, the definition omits what list returns, whether remove is permanent, and how nested conditions are validated or merged with question. The access restriction is the only behavioral detail supplied, leaving real gaps for an agent to discover by trial.

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 75%, so the schema already documents id, question, and conditions, and the baseline applies. The description adds nothing about the action-to-parameter mapping — notably it never states that id is needed for remove or that question/conditions drive add — even though the schema itself leaves action's enum undocumented.

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 gives three concrete verbs (list, add, remove) against a specific resource (the subscriber's saved interest conditions) and clarifies what those conditions are via the parenthetical about mail alerts. It does not name a sibling tool or contrast itself with relax_conditions or check_items, but the resource is distinct enough that an agent can identify it.

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: the person wants to save, see or delete what they follow" maps each of the three actions to an explicit user intent, which is genuinely useful routing guidance. There are no when-not conditions and no pointer to an alternative tool for overlapping needs, so it stops short of 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