Skip to main content
Glama

건강보험료 납부확인서 신청(초기화)

nhis_edi__certificates__health_premium_payment__individual__init

먼저 호출할 도구: nhis_edi__session__login (같은 account_link_id). 연동 계정으로 개인별 건강보험 납부확인서 신청 화면의 신청인 칸, 신청년월 칸, 가입자 명단 표의 열을 받습니다. 칸은 미리 저장해 둔 화면 정보에서 나오며 신청은 하지 않습니다. 로그인한 호출이면 첫 요청 전에 request_idempotency_key 값을 만들어 저장하세요. 응답을 받지 못한 그 요청을 되찾을 때만 같은 인자와 함께 그 값을 다시 보내고, 새로 실행할 때는 새 값을 쓰세요. 이 값 없이 다시 부르면 새 요청이 됩니다. 계정 없이 맛보기로 부를 때는 이 선택 칸을 쓸 수 없습니다. 기관 업무에 따로 있는 idempotency_key 칸은 다른 칸이니 그대로 두세요. 호출마다 토큰 1소진 요청 처리 시 XBOSS 작업을 생성하고 처리 결과를 저장합니다. 기관 원본의 조회 여부와 별개로 이 호출은 순수 읽기 전용이 아닙니다. 기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nhis_edi__certificates__health_premium_payment__individual__init"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
request_idempotency_keyNo로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다.

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. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false, destructiveHint=false; the description goes well beyond that by disclosing that the call creates an XBOSS task, stores a result, consumes one token per call, and is explicitly not pure read-only despite reading screen info. It also spells out the idempotency-key lifecycle (create before first request, reuse only to recover a lost response, new value for a new run). Minor gap: it references an institution-side idempotency_key field that is not in this tool's schema, which adds slight noise rather than contradiction.

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

Conciseness5/5

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

Front-loaded correctly: the prerequisite tool call is the first clause, followed by what the tool returns, then the idempotency contract, then cost and side effects. Each block is short and there is no decorative padding; only the '이 값 없이 다시 부르면 새 요청이 됩니다' sentence mildly restates the preceding rule.

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?

With two optional parameters and no output schema, the definition supplies what an agent needs: prerequisite, returned contents, no side-effect application, token cost, task creation, and idempotency handling. It does not describe the shape of the returned field/column data, but for an init step with no output schema this is a modest gap rather than a blocking one.

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% and the schema itself defers the request_idempotency_key semantics to the description ('쓰는 법은 도구 설명에 있습니다'), so the description must carry that meaning — and it does, explaining creation, reuse-for-recovery, and new-value-per-run. account_link_id is only lightly touched ('로그인한 호출이면'), but the schema already documents its UUID/default-lookup behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific resource (개인별 건강보험 납부확인서 신청 화면) and states exactly what is returned: the applicant field, the application year-month field, and the column list of the subscriber table. It also makes the crucial scope distinction that it only reads pre-saved screen metadata and does not submit an application ('신청은 하지 않습니다'). It stops short of naming sibling tools it differs from (e.g. the payment_completion init), so it is clear but not fully differentiated.

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?

A prerequisite is stated explicitly and unambiguously: call nhis_edi__session__login first with the same account_link_id. It also states a usage boundary — that the optional idempotency field cannot be used for anonymous trial calls. What is missing is routing guidance against alternatives, i.e. when to pick this init versus another certificate init or issue tool.

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