XBOSS

국민연금보험료 요약 조회

nps_edi__b1__national_pension_premiums__summary

Read-only

REQUIRES prior nps_edi__auth__npki_session__login call with same account_link_id. Get national pension premium summary. 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
`row_key`	No	Stable row key from prior list
`row_index`	No	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)
`template_code`	No	Template code (서식 코드)
`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
`cell_text_contains`	No	Partial cell 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"
+}

Changed1 schema field changedOct 15, 2026

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)"

AddedOct 10, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already cover the read-only safety profile, and the description adds genuinely non-structured behavior: an auth prerequisite tied to account_link_id, a per-call quota cost ('호출마다 토큰 1소진'), and a full idempotency-key lifecycle including the rule that reusing the key with the same arguments only recovers a lost response. The idempotency paragraph is verbose and the phrase 'anonymous taste calls' is opaque, but the disclosure goes well beyond the annotations.

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?

The auth prerequisite is correctly front-loaded, but the core purpose sentence is buried after it, and the idempotency block runs five sentences with restatement ('Without it, calling again remains a new request'). The trailing Korean quota note reads as an appended afterthought rather than integrated structure.

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 tool with no output schema and fully documented parameters, the auth, idempotency, and cost context is adequate. It does not explain what the summary contains or where the 'prior list' that supplies row_key/row_index/template_code comes from, leaving a real gap for a 9-parameter tool.

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 the baseline is 3; the description earns above that by supplying the actual semantics for request_idempotency_key, whose schema entry merely says 'see the tool description'. It also clarifies that account_link_id must match the login session, and separates it from a provider-specific idempotency_key field.

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 specific verb and resource: 'Get national pension premium summary'. However, it never distinguishes itself from close siblings such as national_pension_premiums__payment_history, __subscribers, __retro_payments, or __support_details, so an agent must infer which premium view it wants.

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?

The prerequisite is explicit ('REQUIRES prior nps_edi__auth__npki_session__login call with same account_link_id'), which is real routing guidance. But there is no statement of when to choose this summary over the sibling premium lookups, so usage against alternatives 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 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?