Skip to main content
Glama

내만집 (nmjib) — Korean semi-self interior renovation

by com.nmjib
OverviewDiscussionsAdmin

집주인 상담·작업자 매칭 문의(접수 1단계)

nmjib_consult_request
Idempotent

집주인이 내만집 담당자와 상담(반셀프 견적·공정별 작업자 매칭·공정 계획)을 원할 때 문의를 접수한다. 저장만 하고 되읽지 않는다. 호출하면 휴대폰으로 6자리 확인 문자가 가고 접수번호가 온다 → 문자의 번호를 받아 nmjib_verify_code 로 완료한다. 사용자가 명시적으로 "상담 받고 싶다/작업자 연결해 달라/연락 달라"고 할 때만 쓴다(이름·연락처·지역·평수·공사 범위를 물어보고 동의를 받은 뒤 consent=true). 작업자가 필요한 공정이 정해져 있으면 trades 에 넣는다(예: ["타일","도배"]). 금액 산출 도구가 아니다 — 비용 질문은 nmjib_cost_reference(후기 집계 범위)를 쓰고, 정확한 우리집 금액은 앱 견적을 안내한다. 작업자 명단·연락처를 돌려주는 기능은 없다.

Input Schema

NameRequiredDescriptionDefault
nameYes이름(또는 상호 담당자)
noteNo메모
phoneYes휴대폰 번호(010-1234-5678) — 이 번호로 6자리 확인 문자가 갑니다
scopeYes공사 범위. 예: "올수리", "욕실+주방", "도배·마루만"
pyeongNo평수
regionYes지역(시·구)
timingNo공사 희망 시기
tradesNo작업자가 필요한 공정(한글). 가능: 철거, 설비, 창호, 에어컨 청소, 에어컨 설치, 전기, 목공, 타일, 도장, 필름, 도배, 마루, 가구, 도기, 욕실, 마감. 예: ["타일","욕실"]
complexNo아파트·단지명
consentYes개인정보 수집·이용 동의. 사용자에게 수집 항목·목적·보유기간을 읽어 주고 명시적으로 동의를 받은 뒤에만 true. 수집 항목: 이름·휴대폰 번호와 신청 내용 · 목적: 담당자 연락과 접수 처리 · 보유: 180일 뒤 자동 삭제(요청 시 즉시) · 문의·철회: 1644-7233 · 정책: https://nmjib.com/privacy-policy

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / trades / description
      Previous value: -"작업자가 필요한 공정(한글). 가능: 철거, 설비, 창호, 에어컨, 전기, 목공, 타일, 도장, 필름, 도배, 마루, 가구, 도기, 욕실, 마감. 예: [\"타일\",\"욕실\"]"New value: +"작업자가 필요한 공정(한글). 가능: 철거, 설비, 창호, 에어컨 청소, 에어컨 설치, 전기, 목공, 타일, 도장, 필름, 도배, 마루, 가구, 도기, 욕실, 마감. 예: [\"타일\",\"욕실\"]"
  2. Changed1 schema field changed
    • addedInput schema / properties / trades
      Added value: +{
+  "description": "작업자가 필요한 공정(한글). 가능: 철거, 설비, 창호, 에어컨, 전기, 목공, 타일, 도장, 필름, 도배, 마루, 가구, 도기, 욕실, 마감. 예: [\"타일\",\"욕실\"]",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 10,
+  "type": "array"
+}
  3. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false); the description adds the real behavioural payload: it saves without readback, sends a 6-digit SMS to the phone, returns a receipt number, and must be completed via nmjib_verify_code. The consent/privacy precondition and the explicit 'no worker contacts returned' limit are exactly the kind of side-effect disclosure annotations cannot carry.

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?

Dense but every clause is functional: the two-step handoff, the consent gate, the trades conditional, and the cost-tool exclusion each prevent a distinct failure mode. The core action is front-loaded in the first sentence, with constraints following in descending priority.

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

Completeness5/5

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

For a 10-parameter write tool with no output schema, the description supplies what the schema cannot: the return value (접수번호), the completion path (nmjib_verify_code), the SMS side effect, and the consent obligation. An agent has everything needed to invoke it and continue the flow.

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 description coverage is 100%, so the schema already documents all ten parameters including the trades vocabulary and the consent fields, which sets the baseline at 3. The description adds genuine routing value beyond that by stating the conditional for trades ('작업자가 필요한 공정이 정해져 있으면 trades 에 넣는다') and the order in which the other fields should be collected.

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 and resource (집주인 상담·작업자 매칭 문의를 접수한다) and scopes it precisely. It explicitly distinguishes itself from siblings by naming nmjib_cost_reference for cost questions and declaring it does not return worker lists/contacts, so an agent can route without opening another schema.

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 trigger condition ('사용자가 명시적으로 상담 받고 싶다/작업자 연결해 달라/연락 달라 할 때만') plus a prerequisite sequence (ask for name/contact/region/pyeong/scope, get consent, then consent=true). It also names the alternative for a neighbouring intent (금액 질문은 nmjib_cost_reference), covering when-not-to-use.

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

All 내만집 (nmjib) — Korean semi-self interior renovation toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources