Skip to main content
Glama

직원 자격상실 가입자 조회

fourinsure__b1__member_qualification__los_member_lookup

먼저 호출할 도구: fourinsure__session__login (같은 account_link_id). 자격상실 신고서를 쓰기 전에 성명과 주민등록번호로 가입자를 조회해 자격키(rrkey)와 보험별 기존 자격취득일·상실일, 기존 신고 여부를 돌려줍니다. 조회만 하며 기관에 저장하거나 제출하지 않습니다. 로그인한 호출이면 첫 요청 전에 request_idempotency_key 값을 만들어 저장하세요. 응답을 받지 못한 그 요청을 되찾을 때만 같은 인자와 함께 그 값을 다시 보내고, 새로 실행할 때는 새 값을 쓰세요. 이 값 없이 다시 부르면 새 요청이 됩니다. 계정 없이 맛보기로 부를 때는 이 선택 칸을 쓸 수 없습니다. 기관 업무에 따로 있는 idempotency_key 칸은 다른 칸이니 그대로 두세요. 호출마다 토큰 1소진 요청 처리 시 XBOSS 작업을 생성하고 처리 결과를 저장합니다. 기관 원본의 조회 여부와 별개로 이 호출은 순수 읽기 전용이 아닙니다. 기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다.

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": {
      "applicant_name": "<applicant_name>",
      "resident_registration_number": "<resident_registration_number>"
    },
    "name": "fourinsure__b1__member_qualification__los_member_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
bpmnoNo사업장관리번호. 입력하지 않으면 자격상실 신고 화면의 값을 씁니다.
rrno_backNo주민등록번호 뒤 7자리.
rrno_frontNo주민등록번호 앞 6자리.
applicant_nameYes대상자 성명(한글).
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
declaration_apply_dateNo신고 적용일 YYYYMMDD 또는 YYYY-MM-DD. 입력하지 않아도 됩니다.
request_idempotency_keyNo로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다.
resident_registration_numberYes주민등록번호 13자리.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / request_idempotency_key / description
      Previous value: -"Optional same-request recovery key for authenticated calls; see the tool description."New value: +"로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다."
  2. Changed6 schema fields changed
    • changedInput schema / properties / applicant_name / description
      Previous value: -"Member name in Korean."New value: +"대상자 성명(한글)."
    • changedInput schema / properties / bpmno / description
      Previous value: -"Workplace management number. Optional; taken from the loss form when omitted."New value: +"사업장관리번호. 입력하지 않으면 자격상실 신고 화면의 값을 씁니다."
    • changedInput schema / properties / declaration_apply_date / description
      Previous value: -"Declaration date YYYYMMDD or YYYY-MM-DD. Optional."New value: +"신고 적용일 YYYYMMDD 또는 YYYY-MM-DD. 입력하지 않아도 됩니다."
    • changedInput schema / properties / resident_registration_number / description
      Previous value: -"13-digit resident registration number."New value: +"주민등록번호 13자리."
    • changedInput schema / properties / rrno_back / description
      Previous value: -"Resident registration number last 7 digits."New value: +"주민등록번호 뒤 7자리."
    • changedInput schema / properties / rrno_front / description
      Previous value: -"Resident registration number first 6 digits."New value: +"주민등록번호 앞 6자리."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, and the description explains why: each call consumes a token, creates an XBOSS job, and stores the result, so it is not purely read-only despite being a lookup. It also discloses that nothing is saved or submitted to the institution and explains the idempotency-key retry semantics. This is strong added context, though the '조회만 하며' phrasing sits in mild tension with '순수 읽기 전용이 아닙니다' and could confuse an agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The prerequisite is correctly front-loaded, but the body is long and repetitive, especially the multi-sentence idempotency-key explanation and the closing caveats about XBOSS jobs and institutional procedures. Several sentences could be compressed without losing meaning.

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 8-parameter lookup with no output schema, the description covers the return payload, the login prerequisite, the token cost, and the idempotency behavior, which is enough for an agent to call it correctly. Minor gaps remain around what happens when the member is not found and how bpmno defaults interact with the lookup.

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 real meaning beyond the schema: it explains how request_idempotency_key is used for retrying an unanswered request versus a fresh call, and notes that the account-less trial mode cannot use that field. It also warns not to confuse it with the institution's own idempotency_key field.

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 states a specific verb and resource (자격상실 가입자 조회 by 성명 and 주민등록번호) and enumerates what it returns: 자격키(rrkey), 보험별 기존 자격취득일·상실일, 기존 신고 여부. This clearly separates it from the sibling acqs_member_lookup (자격취득) and from the los_save/los_init write tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit prerequisite (call fourinsure__session__login first with the same account_link_id) and a clear trigger (before writing the 자격상실 신고서). It does not name a when-not-to-use case or point to a specific alternative lookup, so it falls short of a 5.

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.

Resources