Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

연금통지서 상세 조회

nps_edi__b1__pension_notification_documents__detail
Read-only

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소진

Input Schema

NameRequiredDescriptionDefault
page_noNoMember list page number (default 1).
row_keyNoRow key from a prior search options[].row_key (e.g. wediDocNo).
row_indexNoRow index from a prior search options[].row_index (search first, or same session right after search).
receipt_noNoReceipt electronic document number (rcptnWediDocNo).
document_noNoElectronic document number (wediDocNo).
member_nameNoMember name for the detail member search.
mark_as_readNoMark as read on view (default true).
include_guideNoInclude guide_rows (default true).
template_codeNoTemplate (document form) code. Search treats A / ALL / 전체 as all documents; detail supports ED33 only (others return UNSUPPORTED_PENSION_NOTIFICATION_TEMPLATE).
page_per_countNoMember list rows per page (default 10).
account_link_idNoAccount link ID (UUID v4). Optional — the server auto-resolves from your API key when omitted. Provide explicitly only when you have multiple certificates for the same provider. Each institution has a separate ID (Hometax != NHIS != NPS != FourInsure).
search_type_codeNoMember search type code for the detail.
row_text_containsNoPartial row text match filter.
member_resident_noNoMember resident registration number for the detail member search.
include_export_rowsNoInclude export_rows (default true).
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed17 schema fields changed
    • removedInput schema / properties / cell_text_contains
      Removed value: -{
-  "description": "Partial cell text match",
-  "type": "string"
-}
    • addedInput schema / properties / document_no
      Added value: +{
+  "description": "Electronic document number (wediDocNo).",
+  "type": "string"
+}
    • addedInput schema / properties / include_export_rows
      Added value: +{
+  "description": "Include export_rows (default true).",
+  "type": "boolean"
+}
    • addedInput schema / properties / include_guide
      Added value: +{
+  "description": "Include guide_rows (default true).",
+  "type": "boolean"
+}
    • removedInput schema / properties / installment_round
      Removed value: -{
-  "description": "Installment round (회차)",
-  "type": "integer"
-}
    • addedInput schema / properties / mark_as_read
      Added value: +{
+  "description": "Mark as read on view (default true).",
+  "type": "boolean"
+}
    • addedInput schema / properties / member_name
      Added value: +{
+  "description": "Member name for the detail member search.",
+  "type": "string"
+}
    • addedInput schema / properties / member_resident_no
      Added value: +{
+  "description": "Member resident registration number for the detail member search.",
+  "type": "string"
+}
    • removedInput schema / properties / notice_year_month
      Removed value: -{
-  "description": "Notice year-month YYYYMM",
-  "type": "string"
-}
    • addedInput schema / properties / page_no
      Added value: +{
+  "description": "Member list page number (default 1).",
+  "type": "integer"
+}
    • addedInput schema / properties / page_per_count
      Added value: +{
+  "description": "Member list rows per page (default 10).",
+  "type": "integer"
+}
    • addedInput schema / properties / receipt_no
      Added value: +{
+  "description": "Receipt electronic document number (rcptnWediDocNo).",
+  "type": "string"
+}
    • changedInput schema / properties / row_index / description
      Previous value: -"Row index the prior list returned for the chosen row - echo that value back as-is (not necessarily 0-based; e.g. NPS rows are 1-based rnum)"New value: +"Row index from a prior search options[].row_index (search first, or same session right after search)."
    • changedInput schema / properties / row_key / description
      Previous value: -"Stable row key from prior list"New value: +"Row key from a prior search options[].row_key (e.g. wediDocNo)."
    • changedInput schema / properties / row_text_contains / description
      Previous value: -"Partial row text match"New value: +"Partial row text match filter."
    • addedInput schema / properties / search_type_code
      Added value: +{
+  "description": "Member search type code for the detail.",
+  "type": "string"
+}
    • changedInput schema / properties / template_code / description
      Previous value: -"Template code (서식 코드)"New value: +"Template (document form) code. Search treats A / ALL / 전체 as all documents; detail supports ED33 only (others return UNSUPPORTED_PENSION_NOTIFICATION_TEMPLATE)."
  2. Changed1 schema field changed
    • addedInput schema / properties / request_idempotency_key
      Added value: +{
+  "description": "Optional same-request recovery key for authenticated calls; see the tool description.",
+  "maxLength": 128,
+  "minLength": 1,
+  "pattern": "^[\\x20-\\x7E]+$",
+  "type": "string"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / row_index / description
      Previous value: -"0-based row index from prior list"New value: +"Row index the prior list returned for the chosen row - echo that value back as-is (not necessarily 0-based; e.g. NPS rows are 1-based rnum)"
  4. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true/destructiveHint=false, so the safety profile is covered. The description adds real value beyond that: an auth prerequisite, idempotency-key lifecycle semantics, and a per-call cost note ('호출마다 토큰 1소진'). It stops short of describing the return payload or pagination behavior.

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

Conciseness3/5

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

It correctly front-loads the login prerequisite, but then spends multiple sentences on generic idempotency boilerplate that could be compressed, and contains an unclear/typo phrase ('anonymous taste calls'). Signal-to-noise is mediocre for an operation whose essentials are auth + row lookup.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only detail tool with 16 optional parameters and no output schema, the description covers auth, idempotency, and cost but never indicates what the detail response contains or how it differs from the search/list output. It is adequate but leaves the agent guessing about the returned document structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 16 parameters thoroughly. The description adds only idempotency_key semantics (reuse vs new key, provider-specific key distinction), which is a marginal contribution over the schema, so baseline 3 applies.

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 clear verb+resource: 'Get detailed pension notification document,' which is specific and distinct from the sibling nps_edi__b1__pension_notification_documents__search by the detail qualifier. However, it never explicitly contrasts itself with the search sibling or the pension_notices__select tool, leaving the agent to infer the search-then-detail relationship.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a genuine precondition ('REQUIRES prior npki_session__login ... with same account_link_id') and extensive idempotency-key guidance. But it never states when to use this versus the search sibling, and the row_key/row_index prerequisites that actually gate invocation ('search first') appear only in the schema, not the description.

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

All XBOSS toolsInspect
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