Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

국민연금 가입자 조회

nps_edi__b1__national_pension_premiums__subscribers
Read-only

REQUIRES prior nps_edi__auth__npki_session__login call with same account_link_id. Get national pension subscribers list. 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
row_keyNoStable row key from prior list
row_indexNoRow 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)
template_codeNoTemplate code (서식 코드)
output_formatsNoOptional. Also return this result as a file (Excel (xlsx)) in artifacts[] of the result. Omit it for data only.
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).
installment_roundNoInstallment round (회차)
notice_year_monthNoNotice year-month YYYYMM
row_text_containsNoPartial row text match
cell_text_containsNoPartial cell text match
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. 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)"
  3. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with that (nothing here mutates data). Beyond annotations it discloses substantial behavior: file artifacts only when output_formats is requested, a 15-minute download_url, 7-day file retention, recovery_receipt handling for anonymous results, and an explicit per-call token cost. Much of this is generic boilerplate shared across the suite rather than specific to this lookup, which keeps it from a 5.

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 actual purpose is a single short sentence buried behind a prerequisite clause and followed by a dense, semicolon-chained block about recovery receipts, idempotency keys, and retention that runs far longer than the tool's own behavior warrants. Most of the text does not earn its place for this specific tool.

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 10-parameter, no-output-schema read tool, the auth prerequisite, artifact behavior, and cost note are covered. However, the central workflow — how row_key/row_index from a prior list feed into this call, and what the returned subscriber rows look like — is never explained, so an agent must infer the selection pattern.

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 all ten parameters are already documented at the schema level and baseline is 3. The description does add marginal meaning for output_formats (xlsx only, artifacts[]) and carries the full explanation for request_idempotency_key, whose schema entry just says "see the tool description" — but it says nothing about row_key/row_index/template_code semantics.

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 sentence "Get national pension subscribers list" names a specific verb and resource, so the agent can tell what it retrieves. It never distinguishes itself from the closely-named siblings nps_edi__b1__certificates__membership__subscribers__search and nps_edi__b1__lookups__workplace_subscribers__status, leaving disambiguation to 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 states a hard prerequisite ("REQUIRES prior nps_edi__auth__npki_session__login call with same account_link_id") and routes expired-link recovery to xdata__job__result, which is useful. But there is no guidance on when to call this list versus the other subscriber-list siblings, or what filters to start with, so usage is only implied.

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