XBOSS

신고 처리 결과 조회 (국민연금)

nps_edi__b1__declarations__processing_results__search

Read-only

REQUIRES prior nps_edi__auth__npki_session__login call with same account_link_id. Search declaration processing results from NPS. 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

Name	Required	Description
`page_no`	No	Page number (default: 1)
`end_date`	No	End date YYYYMMDD
`start_date`	No	Start date YYYYMMDD
`template_code`	No	Template code (서식 코드)
`output_formats`	No	Optional. Also return this result as a file (Excel (xlsx)) in artifacts[] of the result. Omit it for data only.
`page_per_count`	No	Items per page (default: 10)
`account_link_id`	No	Account 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).
`installment_round`	No	Installment round (회차)
`notice_year_month`	No	Notice year-month YYYYMM
`row_text_contains`	No	Partial row text match
`request_idempotency_key`	No	Optional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

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

AddedOct 10, 2026

TDQS

A4/5.0

Behavior5/5

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

Goes well past the readOnly/non-destructive annotations: artifact download_url TTL of 15 minutes, 7-day file retention, token cost per call, receipt-based access rules for anonymous results, and the full idempotency-key lifecycle (create before first request, reuse only for lost-response recovery). These are exactly the operational facts an agent needs before invoking.

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?

The purpose and auth requirement are front-loaded, but the body is a dense run-on block carrying cross-tool boilerplate (anonymous receipts, "taste calls," provider-specific idempotency_key disambiguation) that is largely irrelevant to an authenticated NPS search. Sentences are long and comma-chained, e.g. the artifact sentence, making it hard to parse for the operative rules.

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?

Auth requirement, artifact handling, recovery paths, and cost are all covered, which is most of what an agent needs for this read-only search with 11 optional params. What's missing is any hint about result shape, pagination behavior (page_no/page_per_count), or what a "processing result" record contains.

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 most filters are self-documented, but the description adds real meaning for request_idempotency_key (the schema just says "see the tool description") and clarifies the artifact lifecycle triggered by output_formats. It does not explain how the date/notice/installment filters interact.

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?

States a concrete verb+resource: "Search declaration processing results from NPS," and names the mandatory prerequisite login tool. It does not distinguish this from nearby siblings such as nps_edi__b1__pension_notices__search or the lookups__* search tools, so an agent must infer the difference 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 Guidelines4/5

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

Gives explicit preconditions (prior nps_edi__auth__npki_session__login with the same account_link_id), says when to add output_formats versus omit it "for data only," and routes expired links to xdata__job__result. It never says when to prefer this tool over the sibling notice/document search 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?