XBOSS

가입증명서 발급

nps_edi__b1__certificates__membership__issue

Destructive

REQUIRES prior nps_edi__auth__npki_session__login call with same account_link_id. Issue the NPS membership certificate (EC02, Korean only) for one subscriber. IRREVERSIBLE: the certificate is issued at 국민연금공단 and stays in the application results list; there is no cancel action. An issued certificate can be printed again only within 24 hours; after that a new application must be sent first. 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. 호출마다 토큰 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": "nps_edi__b1__certificates__membership__issue"
  }
}

Input Schema

Name	Required	Description
`row_key`	No	options[].row_key from the subscribers list tool
`language`	No	Certificate language. Only ko (Korean) is issued; omit it.
`row_index`	No	options[].row_index from the subscribers list tool
`member_name`	No	Subscriber name. If several share it, pass row_index or row_key instead.
`account_link_id`	No	연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
`confirmation_token`	No	첫 호출이 돌려준 1회용 확인 토큰입니다(오류 WRITE_CONFIRMATION_REQUIRED). 같은 인자에 이 값을 그대로 넣어 다시 호출하면 실행됩니다. 10분 뒤 만료되고 한 번만 쓸 수 있습니다.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations declare readOnlyHint=false and destructiveHint=true; the description goes far beyond them by naming what is irreversible (the certificate exists at 국민연금공단 and stays in the results list), the 24-hour reprint limit, and the fact that each call consumes a token and creates an XBOSS job. The two-phase preview/confirmation protocol, including that the first call does not execute and that altering any argument invalidates the token, is fully disclosed.

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?

Front-loads the hard requirement and the irreversibility warning, then walks through the confirmation flow in call order, which matches how an agent must act. The trailing Korean paragraph about XBOSS job creation and not being pure read-only is partly boilerplate reiteration of the annotations, keeping it short of 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 a destructive, two-phase write tool with no output schema, the description covers everything needed to call it correctly: auth prerequisite, preview-then-confirm mechanics, token invalidation rule, irreversibility, and the post-issue constraints. An agent has no unresolved question about what happens on the first versus second call.

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 real meaning on top by explaining the lifecycle of confirmation_token — that it comes from the preview call, must be paired with identical arguments, that changing an argument voids it, and that omitting it produces a fresh preview. It does not add anything for row_key/row_index/member_name, which is acceptable since the schema documents them.

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?

States a specific verb and resource: "Issue the NPS membership certificate (EC02, Korean only) for one subscriber." It also scopes the operation against adjacent workflows by naming the prerequisite session tool and noting that a new application must be sent first after 24 hours, so an agent can place it relative to the apply/search siblings.

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?

Gives an explicit precondition (a prior npki_session__login call with the same account_link_id) and an explicit absence of alternatives ("there is no cancel action"). It also spells out the follow-up path when the 24-hour reprint window has passed, leaving no inference required.

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

All XBOSS tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?