Skip to main content
Glama
scvcoder

korean-privacy-law-mcp

by scvcoder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

search_privacy_guides

Search official PIPC privacy guides (7 types, 954 chunks) for rules on pseudonym data, CCTV, small business, and sectoral topics. Returns cited excerpts with page info for compliance.

Instructions

PIPC 공식 가이드 7종 BM25 검색 (Contextual Retrieval, 총 954청크). doc_type ∈ {qa, small_business, cctv, sectoral, pseudonym, privacy_policy, public_ax, all}. qa=질의응답 모음집(2025.12, 99) / small_business=소상공인 핸드북(2024.12, 41) / cctv=고정형 영상정보처리기기 안내서(2024.12, 71) / sectoral=분야별 안내서(2024.12, 476, 8개 편 전체: 인사노무·사회복지시설·의료기관·약국·학원교습소·통계작성·공공기관·온라인경품) / pseudonym=가명정보 처리 가이드라인(2026.3, 132: 본권 제도 안내—특례·5단계 절차·위험도 판단·비정형데이터 기준·Q&A + 별권 실무—결합·반출 절차·안전조치·가명처리 기술·서식 10종·운영문서·위험도 판단 예시·AI 시나리오 7종) / privacy_policy=개인정보 처리방침 작성지침(2026.4, 96: 기재사항 24개 항목별 작성법·예시, 공개 방법·라벨링, 생성형 AI 서비스·아동·공공기관·소상공인·업종별 부록) / public_ax=공공 AX 프라이버시 보호 안내서(2026.7, 39: 공공기관 AI 전환 단계별·유형별 점검, 적법근거 해석, 사전적정성 검토 사례). 법제처 API가 못 가진 PIPC 실무 안내가 차별화. 응답에 PIPC attribution + 페이지 정보 자동 첨부 (pipc-attribution 라이선스). 다음: search_privacy_cases로 실제 상담 사례, search_law로 관련 법조문.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes검색 키워드 (예: '가명정보 결합', 'CCTV 화각', '소상공인 동의', '의료기관 적용', '처리방침 국외이전', '공공 AX 적법근거')
displayNo결과 개수 (기본 5, 최대 30)
doc_typeNo가이드 종류 — qa(질의응답 99청크) / small_business(소상공인 41) / cctv(CCTV 안내서 71) / sectoral(분야별 안내서 476, 8개 편 전체) / pseudonym(가명정보 처리 가이드라인 2026.3 본권+별권 132) / privacy_policy(개인정보 처리방침 작성지침 2026.4 96) / public_ax(공공 AX 프라이버시 보호 안내서 2026.7 39) / all(전체 7종 954)all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.9.0
    • changedInput schema / properties / doc_type / description
      Previous value: -"가이드 종류 — qa(질의응답 99청크) / small_business(소상공인 41) / cctv(CCTV 안내서 71) / sectoral(분야별 안내서 476, 8개 편 전체) / all(전체 4종 687)"New value: +"가이드 종류 — qa(질의응답 99청크) / small_business(소상공인 41) / cctv(CCTV 안내서 71) / sectoral(분야별 안내서 476, 8개 편 전체) / pseudonym(가명정보 처리 가이드라인 2026.3 본권+별권 132) / privacy_policy(개인정보 처리방침 작성지침 2026.4 96) / public_ax(공공 AX 프라이버시 보호 안내서 2026.7 39) / all(전체 7종 954)"
    • changedInput schema / properties / doc_type / enum
      Previous value: -[
-  "qa",
-  "small_business",
-  "cctv",
-  "sectoral",
-  "all"
-]New value: +[
+  "qa",
+  "small_business",
+  "cctv",
+  "sectoral",
+  "pseudonym",
+  "privacy_policy",
+  "public_ax",
+  "all"
+]
    • changedInput schema / properties / query / description
      Previous value: -"검색 키워드 (예: '가명정보 결합', 'CCTV 화각', '소상공인 동의', '의료기관 적용')"New value: +"검색 키워드 (예: '가명정보 결합', 'CCTV 화각', '소상공인 동의', '의료기관 적용', '처리방침 국외이전', '공공 AX 적법근거')"
  2. Changed1 schema field changedv0.8.3
    • changedInput schema / properties / doc_type / description
      Previous value: -"가이드 종류 — qa(질의응답 99청크) / small_business(소상공인 41) / cctv(CCTV 안내서 71) / sectoral(분야별 안내서 246) / all(전체 4종 457)"New value: +"가이드 종류 — qa(질의응답 99청크) / small_business(소상공인 41) / cctv(CCTV 안내서 71) / sectoral(분야별 안내서 476, 8개 편 전체) / all(전체 4종 687)"
  3. First observedv0.0.1

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations available, the description carries the full transparency burden. It discloses the retrieval algorithm (BM25 + Contextual Retrieval), corpus scale (954 chunks), the meaning of each doc_type, and automatic attachment of PIPC attribution and page information under the pipc-attribution license. It does not describe result format or failure/limit behaviors, but for a read-only search tool this is strong disclosure.

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?

The description is long but densely structured and front-loaded, leading with the core purpose in the first sentence. It packs doc_type details into readable parenthetical lists and uses routing at the end. Some content repeats the schema's own parameter descriptions, but the description adds dates and detailed content breakdowns not present there.

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 a tool with 3 parameters, no annotations, and no output schema, the description covers corpus provenance, content per doc_type, licensing, and sibling routing. It could additionally describe the shape of returned results or edge cases, but the essentials for correct selection and invocation are present, and attribution behavior is disclosed.

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. The description adds substantial semantic value beyond the schema by explaining what each doc_type refers to, down to document dates, chunk counts, and contents (e.g., pseudonym's main/separate volumes, sectoral's 8 subfields). Query and display parameters receive less added meaning beyond the schema's examples, but doc_type is the high-complexity parameter and is richly annotated.

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: 'PIPC 공식 가이드 7종 BM25 검색 (Contextual Retrieval, 총 954청크)' – a BM25 search over 7 official PIPC guides. It also distinguishes itself from siblings by stating the differentiating value ('법제처 API가 못 가진 PIPC 실무 안내가 차별화') and pointing to alternative tools for nearby tasks.

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?

It provides explicit routing guidance: '다음: search_privacy_cases로 실제 상담 사례, search_law로 관련 법조문', telling the agent when to use sibling tools instead. It also clarifies this tool's unique scope as PIPC practical guidance not covered by the Ministry of Government Legislation API, giving clear selection context, though not exhaustively covering every sibling search tool.

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

Deploy Server

Other Tools