XBOSS

EDI 전자고지 선택

nhis_edi__hr_payroll__edi_electronic_notices__select

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__edi_electronic_notices__select"
  }
}

Input Schema

Name	Required	Description
`unb_no`	No	Identifier returned by the list result; pass it through.
`row_key`	No	Row key returned by the list result; pass it back to select that row.
`to_date`	No	Search range end date (YYYYMMDD).
`from_date`	No	Search range start date (YYYYMMDD).
`row_index`	No	Zero-based index of the row chosen from the list result.
`wrt_chasu`	No	Write sequence (작성차수) from the list result; pass through.
`goji_chasu`	No	Notice round (고지차수).
`goji_yyyymm`	No	Notice year-month (YYYYMM).
`wrt_dup_seq`	No	Write duplicate sequence from the list result; pass through.
`account_link_id`	No	연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
`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

A4.1/5.0

Behavior5/5

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

Beyond the supplied annotations (readOnlyHint=false, destructiveHint=false), the description discloses a lot: the selection is persisted into the login session, each call consumes one token, an XBOSS task is created and its result stored, and it explicitly warns the call is not purely read-only even when the source lookup is. The idempotency paragraph also explains first-use, reuse-for-recovery, and new-key-for-new-execution semantics. This is materially above what the structured fields convey.

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 front-loaded, which is good, but the body mixes Korean and English and carries generic boilerplate (the XBOSS/task sentence, the 'anonymous taste calls' fragment) that reads as template text shared across many tools. The idempotency paragraph is longer than the selection semantics themselves and dilutes the core instruction.

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 an 11-parameter tool with no required fields and no output schema, the description covers the prerequisite chain, the re-search fallback, the side effects, and the cost per call, which is enough to invoke it correctly. The only shortfall is that the return content is only gestured at ('그 고지의 값을 받습니다') rather than characterized, which matters since there is no output schema.

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 adds real meaning by explaining that `row_key`/`row_index`/`goji_yyyymm`/`goji_chasu` are alternative ways to identify a single row taken from the list result, which the schema documents only field-by-field. It also gives the idempotency key lifecycle guidance the schema defers to ('see the tool description'). It does not explain how to resolve conflicts when several identifier groups are supplied.

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: pick one row from the 전자고지 search results by row number/key or 고지 연월·차수, commit it to the login session, and return that notice's values. That is a clear, concrete action an agent can recognize. It does not, however, differentiate itself from the sibling `...electronic_notices__detail` or `...__contract`, so the boundary between 'select' and 'detail' must be inferred.

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?

Explicitly states the precondition (requires a prior `nhis_edi__session__login` call with the same account_link_id) and the fallback path (if the session has no search results, it searches again first). That is solid when-to-use context. The gap is that no alternative or exclusion is named — it never says when to use `detail` instead, or that selecting is a prerequisite for later calls.

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?