Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

건강보험 고지 선택

nhis_edi__hr_payroll__premium_notices__select
Read-only

REQUIRES prior nhis_edi__session__login call with same account_link_id. Select a specific 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
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 them. It adds genuinely non-obvious context: the login/session dependency, the idempotency-key recovery semantics (reuse only to recover a lost response, new key for new execution), and a per-call token cost ('호출마다 토큰 1소진'). It does not describe the response shape or what a successful selection returns.

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 hard requirement is correctly front-loaded, but roughly two-thirds of the text is generic idempotency boilerplate that reads as pack-wide copy rather than tool-specific guidance. The phrase 'anonymous taste calls' is opaque and costs the reader effort without adding information.

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 selection tool with no output schema, the description should cover how rows are identified and what selection yields. Instead it covers auth and idempotency well but leaves the row-selector interaction and return behavior undocumented, which is the part an agent is most likely to get wrong.

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, but the description actually adds meaning for request_idempotency_key (the schema itself defers to the description) and reinforces the account_link_id/login coupling. It does not explain how the four row-selection parameters (row_key, row_index, row_text_contains, cell_text_contains) relate or which takes precedence.

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 ('Select a specific premium notice'), and the parameter set makes clear it operates on a row from a prior list result. It never distinguishes itself from the very close siblings nhis_edi__hr_payroll__premium_notices__search and __detail, so an agent must infer the select-vs-detail boundary from the schema.

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 and front-loaded ('REQUIRES prior nhis_edi__session__login call with same account_link_id'), which is real usage guidance. However, there is no statement of when to choose this over premium_notices__detail or __search, and no exclusions or ordering guidance beyond the login requirement.

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