Skip to main content
Glama

직원 자격취득 가입자 조회

fourinsure__b1__member_qualification__acqs_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__acqs_member_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
applicant_nameYes대상자 성명(한글).
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
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. Changed2 schema fields changed
    • changedInput schema / properties / applicant_name / description
      Previous value: -"Member name in Korean."New value: +"대상자 성명(한글)."
    • changedInput schema / properties / resident_registration_number / description
      Previous value: -"13-digit resident registration number."New value: +"주민등록번호 13자리."
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations it discloses cost (호출마다 토큰 1소진), the side effect of creating an XBOSS job and persisting results, and explicitly warns that the call is not purely read-only despite the institution-side lookup being read-only — consistent with readOnlyHint=false. The idempotency contract is also spelled out: reuse the same key only to recover an unanswered request, use a fresh key for a new run, and omit it for anonymous trial calls.

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 prerequisite is front-loaded and every paragraph carries actionable content, but the read-only framing is split across two widely separated sentences ('조회만 하며 기관에 저장하거나 제출하지 않습니다' vs '순수 읽기 전용이 아닙니다'), which forces the reader to reconcile them rather than stating the nuance in one place.

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 enumerates the returned fields, and it covers auth prerequisite, account linkage, per-call cost, and idempotency recovery — everything an agent needs to invoke this correctly. The side-effect warning closes the one gap the annotations would otherwise leave ambiguous.

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 would be 3, but the description adds real semantics the schema explicitly defers to it ('쓰는 법은 도구 설명에 있습니다') by explaining lifecycle of request_idempotency_key and by warning that the institution's own idempotency_key field is a different field to leave untouched. It does little extra for applicant_name/resident_registration_number beyond what the schema already says.

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 names a specific verb and resource ('자격취득 신고서를 쓰기 전에 성명과 주민등록번호로 가입자를 조회') and enumerates what comes back (rrkey, 대표자 여부, per-insurance 자격취득일/상실일). The scope word '자격취득' plus the prerequisite framing separates it from the sibling lookup tools without the agent needing to open the schema.

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 states an ordering rule up front ('먼저 호출할 도구: fourinsure__session__login (같은 account_link_id)') and places the call in a workflow ('자격취득 신고서를 쓰기 전에'). What it lacks is an explicit when-not case or a named alternative lookup to prefer under different conditions.

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