Skip to main content
Glama

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

자재·가전 업체 입점 문의(접수 1단계)

nmjib_partner_inquiry
Idempotent

자재·가전·조명·가구 업체가 내만집 스토어·견적서 입점을 문의할 때 접수한다. 저장만 하고 되읽지 않는다. 호출하면 담당자 휴대폰으로 6자리 확인 문자가 가고 접수번호가 온다 → 문자의 번호를 받아 nmjib_verify_code 로 완료한다(파트너 입점 페이지 안내 포함). 사용자가 업체 담당자로서 명시적으로 원할 때만 쓴다(회사명·담당자·연락처·분류·품목을 물어보고 동의를 받은 뒤 consent=true). 내만집의 매입 단가·마진·거래 조건은 이 도구가 알려주지 않는다.

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>",
      "company": "<company>",
      "category": "<category>",
      "items": "<items>"
    },
    "name": "nmjib_partner_inquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes이름(또는 상호 담당자)
noteNo메모
emailNo이메일
itemsYes주요 품목
phoneYes휴대폰 번호(010-1234-5678) — 이 번호로 6자리 확인 문자가 갑니다
companyYes회사명
consentYes개인정보 수집·이용 동의. 사용자에게 수집 항목·목적·보유기간을 읽어 주고 명시적으로 동의를 받은 뒤에만 true. 수집 항목: 이름·휴대폰 번호와 신청 내용 · 목적: 담당자 연락과 접수 처리 · 보유: 180일 뒤 자동 삭제(요청 시 즉시) · 문의·철회: 1644-7233 · 정책: https://nmjib.com/privacy-policy
websiteNo웹사이트
categoryYes분류(자재·가전·조명·가구 등)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, it discloses a real side effect (a 6-digit SMS is sent to the manager's phone), the return value (a receipt number), that nothing is read back, and that a second tool completes the flow. That is substantive behavior an agent cannot infer from readOnlyHint=false / idempotentHint=true.

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?

Sentences are front-loaded and each carries distinct operational information; the flow order (collect → consent → call → verify) is clear. The parenthetical "(파트너 입점 페이지 안내 포함)" is slightly ambiguous and could be tightened.

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 explains what comes back (receipt number, SMS), what happens on the backend (store only, no readback), and how to finish. For a 9-parameter mutation with a two-step flow, nothing operationally essential is missing.

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 baseline is 3, but the description adds value by specifying which fields must be collected from the user (회사명·담당자·연락처·분류·품목) and by tying consent=true to an explicit consent ritual. Optional fields like email/website/note are left to 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?

"자재·가전·조명·가구 업체가 내만집 스토어·견적서 입점을 문의할 때 접수한다" names a specific verb (접수), the exact resource (입점 문의), and who it is for. It also distinguishes the step from the completion step handled by nmjib_verify_code.

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?

States a hard gating condition — only when the user explicitly acts as a company representative and has given consent — plus the prerequisite data to collect and the follow-up call to nmjib_verify_code. It also names an exclusion (no purchase price/margin/trade terms), leaving nothing to inference.

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.