Skip to main content
Glama

가입증명 신청서 발송

nps_edi__b1__certificates__membership__apply
Destructive

REQUIRES prior nps_edi__auth__npki_session__login call with same account_link_id. This writes to the institution. The first call is not executed: it returns a preview of exactly what will be sent and a one-time confirmation_token (error WRITE_CONFIRMATION_REQUIRED). Show that preview to the user as it is. Only after the user agrees, call again with the same arguments plus that confirmation_token. Never add the token without the user's agreement. Changing any argument makes the token invalid; call without the token to get a new preview. Send the NPS membership certificate application (form EB0301) for 1 to 100 subscribers. Do this before the issue tool: the issue screen lists subscribers only under a received application document number. IRREVERSIBLE: a sent application cannot be cancelled and stays in the institution's records. Each subscriber needs member_name and rrno (13-digit resident registration number; never echoed back - the preview shows names and the last 4 digits only). 호출마다 토큰 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": {
      "subscribers": "<subscribers>"
    },
    "name": "nps_edi__b1__certificates__membership__apply"
  }
}

Input Schema

NameRequiredDescriptionDefault
subscribersYes신청 대상자 목록(1명 이상 100명 이하). 대상자마다 성명과 주민등록번호를 넣는다
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
confirmation_tokenNo첫 호출이 돌려준 1회용 확인 토큰입니다(오류 WRITE_CONFIRMATION_REQUIRED). 같은 인자에 이 값을 그대로 넣어 다시 호출하면 실행됩니다. 10분 뒤 만료되고 한 번만 쓸 수 있습니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false; the description goes well beyond them by disclosing the preview-first execution model, the WRITE_CONFIRMATION_REQUIRED error, token single-use and argument-invalidation behavior, the irreversibility of a sent application, and the rrno redaction policy. It also explicitly notes this is not a pure read-only call, consistent with readOnlyHint=false.

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 critical constraints (prerequisite, preview-then-confirm, irreversibility) are front-loaded in the first third, with zero filler in the workflow sentences. The trailing Korean boilerplate about a per-call token and XBOSS job creation is generic, awkwardly appended, and partially redundant with the surrounding text, which keeps it from a 5.

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?

For an irreversible write tool with no output schema, the description covers everything an agent needs: authentication prerequisite, confirmation handshake, what the first call returns (preview + token), timeout behavior, ordering relative to the issue tool, and the consequence of success. Nothing material is left to inference.

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 meaning the schema does not: the preview echo policy (names plus last 4 digits of rrno only), that mutating any argument invalidates the token and requires re-fetching a preview, and that 1-100 subscribers is an institutional limit rather than an arbitrary cap.

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?

"Send the NPS membership certificate application (form EB0301) for 1 to 100 subscribers" states a specific verb, resource, form identifier and scope. It also explicitly separates this tool from the issue sibling ("Do this before the issue tool"), so an agent can route correctly without opening either schema.

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 names the prerequisite ("REQUIRES prior nps_edi__auth__npki_session__login call with same account_link_id"), the ordering constraint against the issue tool, and the exact two-step escalation path when the user must be asked to confirm. When-not conditions and the alternative are both present.

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