Skip to main content
Glama

건강보험 공지 목록 조회

nhis_edi__public__notices__list

자격증명이나 로그인 없이 바로 호출할 수 있습니다. 쪽 번호를 넣으면 대외 공지사항 게시판 그 쪽의 글마다 번호나 공지 표시, 제목, 등록일과 글 주소를 받고, 첨부가 있으면 첨부 안내도 받습니다. 연동 계정과 기관 로그인은 필요하지 않습니다. 로그인한 호출이면 첫 요청 전에 request_idempotency_key 값을 만들어 저장하세요. 응답을 받지 못한 그 요청을 되찾을 때만 같은 인자와 함께 그 값을 다시 보내고, 새로 실행할 때는 새 값을 쓰세요. 이 값 없이 다시 부르면 새 요청이 됩니다. 계정 없이 맛보기로 부를 때는 이 선택 칸을 쓸 수 없습니다. 기관 업무에 따로 있는 idempotency_key 칸은 다른 칸이니 그대로 두세요. 호출마다 토큰 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__public__notices__list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo쪽 번호. 기본 1.
request_idempotency_keyNo로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / request_idempotency_key / description
      Previous value: -"Optional same-request recovery key for authenticated calls; see the tool description."New value: +"로그인한 호출에서 응답을 못 받은 같은 요청을 되찾을 때 쓰는 선택 값입니다. 쓰는 법은 도구 설명에 있습니다."
  2. Changed1 schema field changed
    • changedInput schema / properties / page / description
      Previous value: -"Page number (default: 1)"New value: +"쪽 번호. 기본 1."
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, and the description reinforces this by explicitly stating the call is 'not purely read-only' and creating an XBOSS task plus storage. It adds material context beyond annotations: no credentials required, token consumption of 1 per call, and idempotency semantics. Return format is described in prose rather than left to an output schema.

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 no-credential requirement is front-loaded, which is good, but it is stated twice ('자격증명이나 로그인 없이' and '연동 계정과 기관 로그인은 필요하지 않습니다'), and the idempotency instructions sprawl across several sentences. The token-cost and XBOSS details arrive embedded mid-paragraph rather than being cleanly structured.

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 parameter-light read tool with no output schema, the description covers auth requirements, return fields, pagination via page number, idempotency behavior, and cost. The only mild gap is that it emphasizes write-adjacent behavior (XBOSS task) without telling the agent what actually changes, but overall it is complete enough to invoke correctly.

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 substantially enriches the request_idempotency_key parameter: when to mint it, when to reuse vs regenerate, that a guest call cannot use it, and that it is distinct from the institutional idempotency_key field. This is real meaning the schema explicitly defers to ('쓰는 법은 도구 설명에 있습니다').

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: lists posts on the public notice board (대외 공지사항 게시판), and enumerates exactly what each item returns (number/notice marker, title, registration date, post URL, attachment info). This clearly distinguishes it from the institutional/HR notice tools by naming the 'public' board, though it never names an alternative tool explicitly.

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 clear conditional guidance for the idempotency key (logged-in vs guest, new request vs recovery) but provides no when-to-use/when-not guidance relative to sibling notice tools in the catalog. Usage is implied by the 'public' framing rather than stated as a decision rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources