청약 도우미

housing_monitoring_save

Destructive

Replaces all commute and current housing settings for monitoring. Read existing values first and include details to keep; saving does not validate travel times or start alerts.

Instructions

본인의 통근·현재 주거 조건 전체를 교체합니다. 먼저 housing_monitoring_get으로 기존 값을 읽고 유지할 정보를 포함하세요. 통근 조건 저장만으로 실제 이동시간 검증이나 자동 알림이 실행되지는 않습니다.

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": {
      "monitoring": "<monitoring>"
    },
    "name": "housing_monitoring_save"
  }
}

Input Schema

Name	Required	Description	Default
`monitoring`	Yes	개인 통근과 현재 주거 조건을 저장합니다. 알림 조건을 저장해도 자동 알림 서비스가 시작되지는 않습니다.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 6, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and non-idempotent, but the description adds the crucial implication that omission means deletion (read-then-resubmit pattern) and explicitly states that saving does not trigger travel-time verification or automatic alerts. That side-effect disclosure is genuinely useful non-schema information; only the exact response/return behavior is left unstated.

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, front-loaded with the replace semantics, then the required workflow, then the caveat about verification and alerts. No redundant restatement of the title or schema.

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 destructive, single-parameter mutation with no output schema and rich annotations, the description covers the replacement semantics, the required read-first workflow, and the non-obvious 'no automatic validation/alerts' limitation. A brief note on what the call returns (or whether it echoes saved state) would make it complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes further by clarifying the semantics of the single nested 'monitoring' object: it is a wholesale replacement, so every nullable field left out is cleared, not merged. That merge-vs-replace distinction is not stated in the schema and is the most consequential thing an agent must know.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (전체를 교체합니다 – fully replaces) applied to a specific resource (통근·현재 주거 조건 – commute and current housing conditions). It also implicitly distinguishes itself from the read-side sibling by naming housing_monitoring_get as the prerequisite.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit ordering instruction: read existing values with housing_monitoring_get first and re-include anything that should be preserved. This tells the agent both when to use this tool and which alternative to pair it with, leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server