Skip to main content
Glama
Sign In
청약 도우미

청약 도우미

by ANNJUNGCHAN
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

housing_compare

Read-onlyIdempotent

Compare your current home and candidate homes by monthly housing cost and commute time, using saved current conditions when omitted, with assumptions explained and no results saved.

Instructions

현재 집과 후보의 월 환산 주거비·입력된 통근시간을 비교합니다. current를 생략하면 본인의 저장된 현재 주거 조건을 사용합니다. 금리·기회비용 등 가정을 함께 설명하고, 입력하지 않은 통근시간을 검증된 것으로 해석하지 마세요. 결과는 저장하지 않습니다.

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": {
      "candidates": "<candidates>"
    },
    "name": "housing_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
currentNo
candidatesYes
assumptionsNo
maxCommuteMinutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real behavior: results are not persisted, assumptions (interest rate, opportunity cost) are surfaced alongside the result, and un-entered commute times must not be read as verified. That last point is a valuable interpretive constraint an agent would otherwise get wrong.

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?

Four short sentences, front-loaded with what is compared, then the default behavior, then the caveats. No sentence is redundant and each adds distinct information.

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 comparison tool with no output schema and a complex nested input, the description covers the essential semantics: what is compared, the default source for `current`, and the honesty caveat about commute data. The main remaining gap is the assumptions object, whose fields carry no explanation anywhere.

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 0% and the schema is deeply nested, so the description does some work: it explains the `current` omission default and the intended meaning behind commute verification. It says nothing about `assumptions` (loanRate, loanShare, opportunityRate) or `maxCommuteMinutes`, which are the parameters most likely to be mis-set.

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 verb (비교합니다, compares) and specific resources (월 환산 주거비, 통근시간) across 'current' versus 'candidates', so the operation is clear. It does not, however, distinguish itself from calculation siblings such as housing_affordability_calculate or housing_finance_calculate, leaving an agent to infer the boundary.

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

Usage Guidelines3/5

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

One concrete usage rule is given: omitting `current` falls back to the user's saved housing profile, which implicitly points at housing_profile_get. There is no statement of when to prefer this over the other calculation tools, and no exclusion or prerequisite guidance for the candidate/assumption inputs.

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

Deploy Server

Other Tools