Skip to main content
Glama

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

자재 구매·견적 문의(접수 1단계)

nmjib_material_request
Idempotent

집주인이 인테리어 자재(마루·벽지·타일·도기·수전·조명·가전 등)를 내만집을 통해 구매하거나 견적을 받고 싶을 때 문의를 접수한다. 저장만 하고 되읽지 않는다. 호출하면 휴대폰으로 6자리 확인 문자가 가고 접수번호가 온다 → 문자의 번호를 받아 nmjib_verify_code 로 완료한다(담당자가 품목·수량을 확인해 견적을 회신). 사용자가 명시적으로 "자재 견적 받고 싶다/구매하고 싶다"고 할 때만 쓴다(이름·연락처·품목·수량·지역을 물어보고 동의를 받은 뒤 consent=true). 이 도구는 가격·재고·상품 목록을 알려주지 않는다 — 자재 종류·고르는 법은 search 로 매거진을 안내하고, 금액은 담당자 회신 또는 앱 견적으로 안내한다.

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": {
      "name": "<name>",
      "phone": "<phone>",
      "consent": "<consent>",
      "items": "<items>",
      "region": "<region>"
    },
    "name": "nmjib_material_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes이름(또는 상호 담당자)
noteNo메모
itemsYes자재 품목. 예: "강마루 30평", "실크 벽지 거실·방 3", "욕실 타일 600각 + 변기·세면대"
phoneYes휴대폰 번호(010-1234-5678) — 이 번호로 6자리 확인 문자가 갑니다
pyeongNo평수
regionYes현장·배송 지역(시·구)
timingNo필요 시기
complexNo아파트·단지명
consentYes개인정보 수집·이용 동의. 사용자에게 수집 항목·목적·보유기간을 읽어 주고 명시적으로 동의를 받은 뒤에만 true. 수집 항목: 이름·휴대폰 번호와 신청 내용 · 목적: 담당자 연락과 접수 처리 · 보유: 180일 뒤 자동 삭제(요청 시 즉시) · 문의·철회: 1644-7233 · 정책: https://nmjib.com/privacy-policy
quantityNo수량·면적
brand_prefNo선호 브랜드·등급

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnly=false, openWorld=false, idempotent=true, destructive=false, but the description adds real behavior: write-only with no read-back, a 6-digit SMS verification sent to the phone, a returned 접수번호, and staff follow-up with a quote. The single gap is that repeated calls each trigger an SMS and a new 접수번호, which sits slightly uneasily with idempotentHint=true without being explained.

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?

Front-loads the purpose, then behavior, then usage gate, then exclusions, so the most decision-relevant content comes first. It is dense but nearly every clause carries information; the only mild redundancy is restating the consent requirement already enforced by the 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 an 11-parameter write tool with no output schema, the description covers the two-step flow, the return value (접수번호), the SMS side effect, and what happens next, which is what an agent needs to call it correctly. It leaves failure modes (wrong phone number, expired code) unaddressed, though nmjib_verify_code presumably handles those.

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 100% and every field including consent's collection purpose, retention period, and policy URL is already documented in the schema, so the baseline is 3. The description contributes only a collection checklist (이름·연락처·품목·수량·지역) and adds no formatting or validation nuance beyond the schema.

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 (접수한다 + 인테리어 자재 구매·견적 문의), enumerates example material categories, and explicitly says what it does NOT do (가격·재고·상품 목록을 알려주지 않는다). It also positions itself against siblings by naming search for catalog browsing and nmjib_verify_code as the completion step.

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 gate: use only when the user says '자재 견적 받고 싶다/구매하고 싶다', and requires collecting name/contact/items/quantity/region plus consent before consent=true. It also routes excluded needs elsewhere (자재 종류·고르는 법 → search, 금액 → 담당자 회신 또는 앱 견적), so an agent knows when not to use it.

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.