Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

연금통지서 목록 조회

nps_edi__b1__pension_notification_documents__search
Read-only

REQUIRES prior nps_edi__auth__npki_session__login call with same account_link_id. Search pension notification documents. Files: a document generated from this result, as Excel (xlsx) only when requested in output_formats, listed in artifacts[] of the result with a download_url that works for 15 minutes; each file is kept for 7 days. If a link has expired, call xdata__job__result with the job_id from the result for fresh links. For an anonymous result, keep its private recovery_receipt and send it with the original job_id or pack_run_id to xdata__job__result. It grants access to that result only, until the original file retention expires. Do not publish it. Losing it cannot be repaired by signing up. The receipt also works if the client later signs in; it does not grant access to other results. Without a receipt, results require the original account and lane. 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).
end_dateNoSearch end date YYYYMMDD. Defaults to today when omitted.
start_dateNoSearch start date YYYYMMDD. Defaults to 90 days before today when omitted.
member_nameNoMember name for the detail member search.
template_codeNoTemplate (document form) code. Search treats A / ALL / 전체 as all documents; detail supports ED33 only (others return UNSUPPORTED_PENSION_NOTIFICATION_TEMPLATE).
output_formatsNoOptional. Also return this result as a file (Excel (xlsx)) in artifacts[] of the result. Omit it for data only.
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).
read_status_codeNoRead status: 01=unread, 05=read, 10=all (read+unread), blank=all.
row_text_containsNoPartial row text match filter.
member_resident_noNoMember resident registration number for the detail member search.
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • changedInput schema / properties / end_date / description
      Previous value: -"End date YYYYMMDD"New value: +"Search end date YYYYMMDD. Defaults to today when omitted."
    • removedInput schema / properties / installment_round
      Removed value: -{
-  "description": "Installment round (회차)",
-  "type": "integer"
-}
    • 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"
-}
    • changedInput schema / properties / page_no / description
      Previous value: -"Page number (default: 1)"New value: +"Member list page number (default 1)."
    • changedInput schema / properties / page_per_count / description
      Previous value: -"Items per page (default: 10)"New value: +"Member list rows per page (default 10)."
    • addedInput schema / properties / read_status_code
      Added value: +{
+  "description": "Read status: 01=unread, 05=read, 10=all (read+unread), blank=all.",
+  "type": "string"
+}
    • changedInput schema / properties / row_text_contains / description
      Previous value: -"Partial row text match"New value: +"Partial row text match filter."
    • changedInput schema / properties / start_date / description
      Previous value: -"Start date YYYYMMDD"New value: +"Search start date YYYYMMDD. Defaults to 90 days before today when omitted."
    • 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
    • addedInput schema / properties / output_formats
      Added value: +{
+  "description": "Optional. Also return this result as a file (Excel (xlsx)) in artifacts[] of the result. Omit it for data only.",
+  "items": {
+    "enum": [
+      "xlsx"
+    ],
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array",
+  "uniqueItems": true
+}
  4. Added

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare a safe read, and the description adds real context beyond them: the auth prerequisite, the xlsx artifact behavior with a 15-minute download_url and 7-day retention, job-based link recovery, and the '호출마다 토큰 1소진' cost. The disclosure is substantial, though much of it concerns artifact/receipt mechanics that only apply in narrow cases, and the anonymous-receipt material is irrelevant to an authenticated NPS EDI tool and risks confusing the agent.

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

Conciseness2/5

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

One short sentence states the actual purpose; the rest is a dense block mixing file retention, recovery_receipt handling, pack_run_id/anonymous-result rules, idempotency-key policy, and a Korean token-cost note. Much of it appears copied from a generic artifact/job tool, is not front-loaded, and buries the operation the agent needs.

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

Completeness2/5

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

With 12 parameters, no required fields and no output schema, the description should explain what the search returns (document list fields, pagination) and how filters combine. Instead it spends most of its length on artifact downloads and anonymous recovery receipts, and never describes the returned document list, leaving a real gap for a zero-required-param search.

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 explains page_no, dates, template_code, output_formats, read_status_code and account_link_id. The description adds only the idempotency-key lifecycle, which the schema already points back to, and says nothing about the other eleven parameters. 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?

After a prerequisite sentence it states a specific verb+resource: 'Search pension notification documents.' That is clear enough for an agent to know the operation, but it never distinguishes itself from the sibling pension_notification_documents__detail or from pension_notices__search, so the agent must infer the boundary from the name alone.

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 one real usage rule (must be preceded by nps_edi__auth__npki_session__login with the same account_link_id), which is genuinely useful. However, it offers no guidance on when to call this versus the detail sibling or the other notice-search tools, and no guidance on optional filters such as date ranges or read status.

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