Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

건강보험료 요약 조회

nhis_edi__hr_payroll__health_premiums__summary
Read-only

REQUIRES prior nhis_edi__session__login call with same account_link_id. Get health insurance 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

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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/destructiveHint, so the safety profile is covered; the description adds non-trivial context beyond that: login prerequisite, per-call token cost ('호출마다 토큰 1소진'), and detailed idempotency-key semantics including lost-response recovery. Some phrasing ('anonymous taste calls', provider-specific idempotency_key distinction) is cryptic, 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Good front-loading with REQUIRES placed first, but the idempotency block spans several sentences with redundant restatement ('Without it, calling again remains a new request') and a confusing aside about provider-specific idempotency_key. It is functional but not tight.

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?

For a read-only retrieval tool with full schema coverage, the description covers the critical operational facts an agent needs before calling: auth prerequisite, token cost, and idempotency handling. It does not describe what the 'summary' returns, but with the params implying a per-row drill-down this is a modest gap rather than a blocking one.

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 params (row_key, row_index, goji_round, notice_year_month) are already documented, establishing a baseline of 3. The description goes beyond the schema specifically for request_idempotency_key, which the schema explicitly delegates to the tool description ('see the tool description'), adding genuine generation/reuse guidance.

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 clear verb+resource ('Get health insurance premium summary'), which is specific enough for an agent to recognize the operation. However, it does not distinguish this from close siblings such as nhis_edi__hr_payroll__health_premiums__employee_details or the premium_notices family, so the boundary is left to inference.

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 gives a prerequisite ('REQUIRES prior nhis_edi__session__login') and hints at an anonymous/trial mode, but never states when to choose this summary over employee_details or the premium_notices search/detail siblings. Usage is implied by the tool name rather than explained.

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