Skip to main content
Glama

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

시공 작업자 등록 신청(접수 1단계)

nmjib_worker_apply
Idempotent

시공 작업자(팀·개인)가 내만집에 등록을 신청한다. 저장만 하고 아무 데이터도 되읽지 않는다. 호출하면 신청자 휴대폰으로 6자리 확인 문자가 가고, 응답에 접수번호가 온다 → 사용자에게 문자의 번호를 물어 nmjib_verify_code 로 완료한다(그때 담당자에게 전달). 사용자가 스스로 "내만집에 작업자로 등록하고 싶다/작업 받고 싶다"고 할 때만 쓴다(먼저 이름·연락처·공정·지역을 물어보고, 개인정보 수집·이용 안내를 읽어 준 뒤 동의(consent=true)를 받는다). 가능한 공정: 철거, 설비, 창호, 에어컨 청소, 에어컨 설치, 전기, 목공, 타일, 도장, 필름, 도배, 마루, 가구, 도기, 욕실, 마감. 등록 뒤 내만집 고객의 공정별 견적 요청이 문자·알림톡으로 온다(수수료 0원). 작업자 검색·조회·연락처 열람 기능은 없다.

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>",
      "trades": "<trades>",
      "regions": "<regions>"
    },
    "name": "nmjib_worker_apply"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes이름(또는 상호 담당자)
noteNo메모
phoneYes휴대폰 번호(010-1234-5678) — 이 번호로 6자리 확인 문자가 갑니다
tradesYes할 수 있는 공정(한글). 가능: 철거, 설비, 창호, 에어컨 청소, 에어컨 설치, 전기, 목공, 타일, 도장, 필름, 도배, 마루, 가구, 도기, 욕실, 마감. 예: ["타일","욕실"]
consentYes개인정보 수집·이용 동의. 사용자에게 수집 항목·목적·보유기간을 읽어 주고 명시적으로 동의를 받은 뒤에만 true. 수집 항목: 이름·휴대폰 번호와 신청 내용 · 목적: 담당자 연락과 접수 처리 · 보유: 180일 뒤 자동 삭제(요청 시 즉시) · 문의·철회: 1644-7233 · 정책: https://nmjib.com/privacy-policy
regionsYes작업 가능 지역
licensesNo자격·면허
team_sizeNo팀 인원
career_yearsNo경력(년)
contact_prefNo선호 연락 방법(전화·문자·카카오톡)
business_registeredNo사업자등록 여부

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / trades / description
      Previous value: -"할 수 있는 공정(한글). 가능: 철거, 설비, 창호, 에어컨, 전기, 목공, 타일, 도장, 필름, 도배, 마루, 가구, 도기, 욕실, 마감. 예: [\"타일\",\"욕실\"]"New value: +"할 수 있는 공정(한글). 가능: 철거, 설비, 창호, 에어컨 청소, 에어컨 설치, 전기, 목공, 타일, 도장, 필름, 도배, 마루, 가구, 도기, 욕실, 마감. 예: [\"타일\",\"욕실\"]"
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=false); the description adds the material behaviors: an SMS with a 6-digit code is sent on invocation, the response carries a receipt number, and nothing is read back. The downstream effect (quote requests via SMS/alimtalk, 0% fee) is also disclosed. One gap remains: it never says what happens on repeat submissions, despite idempotentHint=true, which an agent may need since each call triggers an SMS.

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?

Purpose and the 'write-only' constraint are front-loaded, then the side effect and next step, then eligibility and intake steps — a sensible ordering. It is dense but nearly every sentence carries decision-relevant content; the trade list is duplicated from the schema, which is the main redundancy.

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 an 11-parameter mutation tool with no output schema, the description compensates well: it states the return content (receipt number), the out-of-band side effect (SMS), the follow-up tool, and the post-registration business consequence. An agent can execute the correct conversational sequence without guessing.

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 adds workflow-level meaning: it tells the agent to collect name, phone, trades and regions first and to obtain explicit consent before setting consent=true, and it lists the acceptable trade values in prose. It mostly restates the schema's own annotations rather than adding new constraints, so it stops short of 5.

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?

The description opens with a specific verb and resource ('시공 작업자... 등록을 신청한다') and immediately clarifies scope: '저장만 하고 아무 데이터도 되읽지 않는다.' It also distinguishes itself from the sibling it hands off to (nmjib_verify_code) and explicitly disclaims lookup/search capabilities.

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?

Explicit triggering condition is given ('사용자가 스스로 ... 등록하고 싶다/작업 받고 싶다 고 할 때만'), along with a required intake sequence (ask name/contact/trade/region, read the privacy notice, obtain consent=true) and the alternative step that completes the flow. When-not guidance is also implied by the negative scope statement about search/lookup features.

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.