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

TableJSON 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
    • addedInput schema / properties / trades
      Added value: +{
+  "description": "작업자가 필요한 공정(한글). 가능: 철거, 설비, 창호, 에어컨, 전기, 목공, 타일, 도장, 필름, 도배, 마루, 가구, 도기, 욕실, 마감. 예: [\"타일\",\"욕실\"]",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 10,
+  "type": "array"
+}
  2. Added

TDQS

A4.1/5.0
Behavior1/5

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

The description transparently discloses save-only behavior, SMS code sending, and the verify_code follow-up, but it also describes an operation that creates a reception and sends an SMS per call. This contradicts the idempotentHint:true annotation, which claims repeated identical calls have the same effect.

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?

The description is front-loaded with the core purpose, then behavior, usage conditions, and exclusions. Every sentence adds operational information, and despite its length it remains a tight, well-structured single-paragraph spec.

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?

With no output schema, the description still tells the agent what happens (6-digit code, reception number, verify step) and what the tool does not do. Combined with the fully described input schema, an agent has everything needed to call it correctly.

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?

The schema covers all 10 parameters with good descriptions, so the baseline is 3. The tool description adds useful situational semantics by explaining when to set trades, the consent workflow, and that it is not for cost estimation, exceeding schema-only guidance.

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 action (receive consultation/worker-matching inquiries), the exact resource (집주인 상담·작업자 매칭), and the scope (reception step 1). It also separates itself from cost estimation and worker-list lookup, making it distinguishable from siblings.

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?

Explicitly says to use only when the user asks for consultation/worker connection/contact, lists the data to collect and the consent requirement, and names nmjib_cost_reference as the alternative for cost questions. This is complete when-vs-alternative guidance.

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