XBOSS

수신문서 목록 조회 옵션

nhis_edi__hr_payroll__received_documents__options

REQUIRES prior nhis_edi__session__login call with same account_link_id. 기간이나 고지 연월을 넣으면 수신문서 목록의 행마다 행 번호, 문서 이름, 고지 연월과 차수, 작성 차수를 받습니다. 문서 안쪽은 열지 않고 행 정보만 돌려줍니다. 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소진 요청 처리 시 XBOSS 작업을 생성하고 처리 결과를 저장합니다. 기관 원본의 조회 여부와 별개로 이 호출은 순수 읽기 전용이 아닙니다. 기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nhis_edi__hr_payroll__received_documents__options"
  }
}

Input Schema

Name	Required	Description
`to_date`	No	To date YYYYMMDD (default: today)
`form_name`	No	Form name filter
`from_date`	No	From date YYYYMMDD (default: 3 months ago)
`goji_round`	No	Notice round (고지 차수)
`account_link_id`	No	연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
`document_status`	No	Document status filter
`notice_year_month`	No	Notice year-month YYYYMM
`row_text_contains`	No	Partial row text match
`cell_text_contains`	No	Partial cell text match
`request_idempotency_key`	No	Optional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description reinforces rather than contradicts that by stating the call is not purely read-only, that each call consumes one token, and that request processing creates an XBOSS job whose result is stored. The idempotency-key paragraph adds real operational context (reuse only to recover a lost response, new key per execution). Some of this reads as pasted boilerplate unrelated to a document listing, which keeps it below 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?

The precondition is correctly front-loaded, but the body is a mix of Korean and English with duplicated concepts (the idempotency key is explained twice, including a garbled 'anonymous taste calls' clause) and XBOSS/token boilerplate that feels transplanted. It is readable but not tight.

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?

With no output schema, the description does the useful work of naming the returned row fields, and it covers auth preconditions and side effects. It is still silent on result size, pagination, ordering, and whether the filters combine as AND, which matters for a ten-parameter listing tool.

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 coverage is 100%, so all ten parameters are already documented, including the account_link_id fallback behavior and request_idempotency_key constraints. The description adds no filter semantics beyond the schema; the returned row fields it lists describe output rather than parameter meaning, so the baseline 3 applies.

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 description states a concrete retrieval behavior: given a period or notice year-month it returns per-row fields (row number, document name, notice year-month and round, authoring round), and it explicitly says the document interior is not opened. That distinguishes it in substance from a detail-style sibling, though the name 'options' is never reconciled with what is really a row listing.

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 only explicit routing rule is the precondition that a prior nhis_edi__session__login call with the same account_link_id is required. The implicit contrast with detail-style siblings ('문서 안쪽은 열지 않고 행 정보만') hints at when to pick this tool, but no sibling is named and there is no when-not guidance or note on filter combinations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All XBOSS tools Inspect

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

Need Help?