Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

건강보험 고지 상세 조회

nhis_edi__hr_payroll__premium_notices__detail
Read-only

REQUIRES prior nhis_edi__session__login call with same account_link_id. Get detailed info of a selected premium notice. 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_keyNoRow key returned by the list result; pass it back to select that row.
to_dateNoSearch range end date (YYYYMMDD).
from_dateNoSearch range start date (YYYYMMDD).
row_indexNoZero-based index of the row chosen from the list result.
goji_roundNoNotice round (고지회차).
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).
notice_year_monthNoNotice year-month (YYYYMM).
row_text_containsNoSelect the row whose full text contains this string.
cell_text_containsNoSelect the row whose cell text contains this string.
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • changedInput schema / properties / cell_text_contains / description
      Previous value: -"Partial cell text match"New value: +"Select the row whose cell text contains this string."
    • addedInput schema / properties / from_date
      Added value: +{
+  "description": "Search range start date (YYYYMMDD).",
+  "type": "string"
+}
    • changedInput schema / properties / goji_round / description
      Previous value: -"Notice round (고지 차수)"New value: +"Notice round (고지회차)."
    • changedInput schema / properties / goji_round / type
      Previous value: -"integer"New value: +"string"
    • changedInput schema / properties / notice_year_month / description
      Previous value: -"Notice year-month YYYYMM"New value: +"Notice year-month (YYYYMM)."
    • 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: +"Zero-based index of the row chosen from the list result."
    • changedInput schema / properties / row_key / description
      Previous value: -"Stable row key from prior list"New value: +"Row key returned by the list result; pass it back to select that row."
    • changedInput schema / properties / row_text_contains / description
      Previous value: -"Partial row text match"New value: +"Select the row whose full text contains this string."
    • addedInput schema / properties / to_date
      Added value: +{
+  "description": "Search range end date (YYYYMMDD).",
+  "type": "string"
+}
  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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds real context the annotations do not: a per-call token cost ("호출마다 토큰 1소진") and the fact that a repeated call without the key becomes a fresh request. It says nothing about what the detail payload contains or whether the notice must be in a particular state.

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 purpose statement is buried mid-paragraph behind an uppercase prerequisite and followed by a long block of generic idempotency boilerplate that would apply to any tool in this pack. Sentences like "Without it, calling again remains a new request" restate the prior clause and the trailing Korean token note is tacked on without 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?

Prerequisite, cost and idempotency behavior are covered, and the read-only annotation removes the need to explain side effects. However, this is a "detail" tool with no output schema, and the description never hints at what the returned notice detail includes or how row_key versus row_index select the row, leaving the return contract underspecified.

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 row_key, row_index, dates, notice_year_month and goji_round are already documented. The description does add meaning beyond the schema for request_idempotency_key, whose own schema entry explicitly defers to the tool description for the reuse/recovery rules, and it clarifies the account_link_id linkage to the login session.

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 detailed info of a selected premium notice" gives a specific verb plus resource, and the word "selected" signals this is the downstream step of the premium_notices search/select flow. It never names the sibling tools (premium_notices__search, premium_notices__select) explicitly, so the differentiation is inferable rather than stated.

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?

"REQUIRES prior nhis_edi__session__login call with same account_link_id" states a hard precondition clearly, and the idempotency paragraph spells out when to reuse versus mint a new key. There is no explicit when-not or sibling-alternative routing, which keeps it below a 5.

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