XBOSS

연금통지서 상세 조회

nps_edi__b1__pension_notification_documents__detail

REQUIRES prior nps_edi__auth__npki_session__login call with same account_link_id. Get detailed pension notification document. For an authenticated call, generate and save request_idempotency_key before the first request. Reuse it with the same arguments only to recover that request after a lost response; use a new key for a new execution. Without it, calling again remains a new request. This optional key is not available to anonymous taste calls. Keep any provider-specific idempotency_key unchanged; it is a different field. 호출마다 토큰 1소진 기본값(mark_as_read=true)으로 조회 대상 문서를 기관에 읽음 처리합니다. 읽음 처리를 원치 않으면 mark_as_read=false 로 호출하세요. 이 기본 호출은 순수 읽기 전용이 아닙니다.

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__pension_notification_documents__detail"
  }
}

Input Schema

Name	Required	Description
`page_no`	No	Member list page number (default 1).
`row_key`	No	Row key from a prior search options[].row_key (e.g. wediDocNo).
`row_index`	No	Row index from a prior search options[].row_index (search first, or same session right after search).
`receipt_no`	No	Receipt electronic document number (rcptnWediDocNo).
`document_no`	No	Electronic document number (wediDocNo).
`member_name`	No	Member name for the detail member search.
`mark_as_read`	No	Mark as read on view (default true).
`include_guide`	No	Include guide_rows (default true).
`template_code`	No	Template (document form) code. Search treats A / ALL / 전체 as all documents; detail supports ED33 only (others return UNSUPPORTED_PENSION_NOTIFICATION_TEMPLATE).
`page_per_count`	No	Member list rows per page (default 10).
`account_link_id`	No	연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
`search_type_code`	No	Member search type code for the detail.
`row_text_contains`	No	Partial row text match filter.
`member_resident_no`	No	Member resident registration number for the detail member search.
`include_export_rows`	No	Include export_rows (default true).
`request_idempotency_key`	No	Optional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A3.8/5.0

Behavior3/5

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

The description carries real behavioral payload beyond the annotations: each call consumes one token, the default marks the document as read at the issuing institution, and the call is explicitly 'not pure read-only' — consistent with readOnlyHint=false. However, the idempotency paragraph is worded confusingly (the 'anonymous taste calls' clause reads like a garbled template), which weakens otherwise strong disclosure.

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 correctly front-loaded and the Korean side-effect warning is unambiguous. The idempotency block is disproportionately long for an optional parameter and contains a puzzling phrase about 'anonymous taste calls', which costs some clarity without making the text unusable.

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 a 16-parameter, all-optional tool with no output schema, the description covers the auth prerequisite, side effects, cost, and idempotency — the risky parts. It does not describe the shape of the returned detail document or what guide_rows/export_rows contain, which is the main remaining gap given the absence of an output schema.

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 already 100%, so a 3 would be the baseline, but the description genuinely adds meaning for two parameters: mark_as_read is explained as institution-side read-marking with a token cost rather than the schema's terse 'Mark as read on view', and request_idempotency_key gets explicit lifecycle semantics (generate before first call, reuse only for recovery, new key per execution).

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 states a concrete verb and resource — 'Get detailed pension notification document' — which is specific enough to distinguish a detail fetch from the sibling search tool. It does not explicitly name the search counterpart as the way to obtain row_key/document_no, relying on the schema for that routing hint.

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 a hard prerequisite ('REQUIRES prior npki_session login call with same account_link_id') and a conditional usage rule for opting out of read-marking via mark_as_read=false. What it lacks is an explicit statement that a prior search invocation is the expected entry path and any exclusion against lookalike notice tools.

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?