Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

수신문서 목록 조회 옵션

nhis_edi__hr_payroll__received_documents__options
Read-only

REQUIRES prior nhis_edi__session__login call with same account_link_id. Get options for received document list in NHIS EDI. 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
to_dateNoTo date YYYYMMDD (default: today)
from_dateNoFrom date YYYYMMDD (default: 3 months ago)
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. Added

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already mark it read-only and non-destructive, yet the description adds real value beyond them: the login prerequisite, the per-call token cost ('호출마다 토큰 1소진'), and precise idempotency semantics (reuse only to recover a lost request, new key for new executions). It still doesn't explain what the returned 'options' represent or pagination/size limits.

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 prerequisite is correctly front-loaded, but the middle section is four sentences of generic idempotency boilerplate that outweighs the actual tool purpose, and the Korean token-cost note is tacked on at the end rather than integrated.

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 options lookup with full schema coverage and no output schema, the definition covers auth prerequisite and cost per call, which is most of what an agent needs. What is missing is any indication of what the 'options' payload contains and how it feeds the subsequent received-documents list call.

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 every parameter including date ranges, goji_round, notice_year_month, and the idempotency key is documented in the schema. The description adds no parameter-level detail beyond echoing the idempotency key guidance, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the resource (received document list) and verb (get options) in NHIS EDI, but 'options' is ambiguous — it could be filter values, dropdown choices, or list metadata. It does not distinguish itself from the sibling nhis_edi__hr_payroll__edi_electronic_notices__search_options or from the associated received_documents list call.

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?

Gives a clear prerequisite (prior session login with the same account_link_id) and detailed idempotency-key procedure, but never says when to call this instead of the sibling search_options/select tools, or what to do after retrieving the options.

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