Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

발송문서 상세 조회

nhis_edi__document_box__sent_documents__detail
Read-only

REQUIRES prior nhis_edi__session__login call with same account_link_id. Get detailed info of a sent document. 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.
firm_symNoWorkplace symbol (사업장기호) from the list result; pass through.
efirm_symNoElectronic workplace symbol from the list result; pass through.
form_codeNoForm code from the list result; pass through to pick the form/row.
row_indexNoZero-based index of the row chosen from the list result.
wrt_chasuNoWrite sequence (작성차수) from the list result; pass through.
wrt_dup_seqNoWrite duplicate sequence from the list result; pass through.
unit_firm_symNoUnit workplace symbol from the list result; pass through.
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).
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • removedInput schema / properties / cell_text_contains
      Removed value: -{
-  "description": "Partial cell text match",
-  "type": "string"
-}
    • addedInput schema / properties / efirm_sym
      Added value: +{
+  "description": "Electronic workplace symbol from the list result; pass through.",
+  "type": "string"
+}
    • addedInput schema / properties / firm_sym
      Added value: +{
+  "description": "Workplace symbol (사업장기호) from the list result; pass through.",
+  "type": "string"
+}
    • addedInput schema / properties / form_code
      Added value: +{
+  "description": "Form code from the list result; pass through to pick the form/row.",
+  "type": "string"
+}
    • removedInput schema / properties / goji_round
      Removed value: -{
-  "description": "Notice round (고지 차수)",
-  "type": "integer"
-}
    • removedInput schema / properties / notice_year_month
      Removed value: -{
-  "description": "Notice year-month YYYYMM",
-  "type": "string"
-}
    • 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."
    • removedInput schema / properties / row_text_contains
      Removed value: -{
-  "description": "Partial row text match",
-  "type": "string"
-}
    • addedInput schema / properties / unit_firm_sym
      Added value: +{
+  "description": "Unit workplace symbol from the list result; pass through.",
+  "type": "string"
+}
    • addedInput schema / properties / wrt_chasu
      Added value: +{
+  "description": "Write sequence (작성차수) from the list result; pass through.",
+  "type": "string"
+}
    • addedInput schema / properties / wrt_dup_seq
      Added value: +{
+  "description": "Write duplicate sequence from the list result; pass through.",
+  "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.9/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, so the safety profile is covered; the description adds non-obvious behavior: an auth precondition tied to account_link_id and a per-call token cost ("호출마다 토큰 1소진"). The idempotency-recovery semantics are also disclosed, though applying them to a read-only lookup is unusual.

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 idempotency block is generic boilerplate that takes roughly half the text and is of marginal relevance to a read-only detail lookup, diluting the two sentences that actually matter.

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 zero-required-parameter, read-only detail tool with no output schema and full schema coverage, the description covers the auth precondition, cost, and idempotency. The one gap is not stating that the list tool must be called first to source row_key/row_index.

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 description coverage is 100%, so baseline is 3, but the schema defers request_idempotency_key explanation to the tool description ("see the tool description") and the description actually delivers it, including the warning not to conflate it with a provider-specific idempotency_key. The nine pass-through row parameters are left entirely to the schema.

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 detailed info of a sent document") which separates it from the sibling list tool by name convention. It does not explicitly say how it differs from nhis_edi__document_box__sent_documents__list, but the singular "a sent document" and the pass-through row parameters make the distinction inferable.

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?

Gives an explicit hard prerequisite (prior nhis_edi__session__login with the same account_link_id) and clear idempotency-key usage conditions, including when to reuse vs. mint a new key. It stops short of naming the list tool as the required predecessor for obtaining row_key, though the schema fields say "from the list result".

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