Skip to main content
Glama

근로복지공단 보험료 부과고지 검색

comwel__info__premium_billing_notice__search

REQUIRES prior comwel__auth__npki_session__login call with same account_link_id. Search COMWEL premium billing notices. 파일: 엑셀(xlsx) · 이 작업의 결과로 만든 문서 - output_formats 로 청할 때만 만듭니다. 결과의 artifacts[] 에 실리고, 내려받기 링크(download_url)는 15분 동안 열리며 파일은 7일 동안 보관됩니다. 링크가 만료되면 결과의 job_id 로 xdata__job__result 를 다시 불러 새 링크를 받습니다. 로그인 없이 받은 결과는 함께 온 recovery_receipt 를 따로 보관했다가, 처음의 job_id 나 pack_run_id 와 함께 xdata__job__result 에 보내세요. 증표로는 그 결과 하나만, 원래 파일 보관 기간이 끝날 때까지 열 수 있습니다. 증표는 공개하지 마세요. 잃어버리면 가입해도 되찾을 수 없습니다. 나중에 로그인해도 증표는 그대로 쓰이고, 다른 결과는 열지 못합니다. 증표가 없으면 처음 계정과 같은 환경(데모 · 정식)에서만 결과를 읽을 수 있습니다. 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

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "billing_year": "<billing_year>",
      "billing_month": "<billing_month>"
    },
    "name": "comwel__info__premium_billing_notice__search"
  }
}

Input Schema

NameRequiredDescriptionDefault
billing_yearYes부과 연도 YYYY.
billing_monthYes부과 월 MM.
output_formatsNo선택 입력입니다. 결과를 엑셀(xlsx) 파일로도 받으려면 입력해 주세요. 파일은 결과의 artifacts[] 에 실립니다. 비워 두면 데이터만 받습니다.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
business_management_noNo사업장관리번호. 사업장을 고를 때 입력합니다. 입력하지 않아도 됩니다.
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / billing_month / description
      Previous value: -"Billing month MM"New value: +"부과 월 MM."
    • changedInput schema / properties / billing_year / description
      Previous value: -"Billing year YYYY"New value: +"부과 연도 YYYY."
    • changedInput schema / properties / business_management_no / description
      Previous value: -"Business management number (optional; selects the workplace)"New value: +"사업장관리번호. 사업장을 고를 때 입력합니다. 입력하지 않아도 됩니다."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: the call creates an XBOSS job and stores its result, is explicitly not purely read-only despite being a search, and consumes one token per call. This is consistent with readOnlyHint=false. It loses a point because a large share of the text is generic artifact/download-link/recovery-receipt boilerplate rather than behavior specific to this search tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The prerequisite is correctly front-loaded, but the body is long, partially bilingual, and padded with artifact retention, download-link expiry, and recovery-receipt rules that partly duplicate the output_formats schema description. Much of it reads as boilerplate text shared across many tools rather than guidance specific to searching billing notices.

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 cover return mechanics (artifacts[], download_url lifetime, job_id recovery via xdata__job__result), which is genuinely useful. However, it never says what the search itself returns - the notice list shape, filtering behavior, or result size/pagination - which is the core gap for a search tool with 6 parameters.

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 baseline is 3, but the description adds genuine meaning the schema lacks: the request_idempotency_key must be generated and saved before the first request, reused only to recover a lost response, replaced for a new execution, and is unavailable to anonymous calls, with a note that provider-specific idempotency_key is a distinct field. Remaining 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 ("Search COMWEL premium billing notices") plus the concrete scope of the search implied by the required billing_year/billing_month. It does not explicitly contrast with the sibling comwel__info__premium_billing_notice__detail, so the boundary between searching and fetching a single notice is left to the name alone.

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?

The prerequisite is stated unambiguously and up front: a prior comwel__auth__npki_session__login call with the same account_link_id is required. It also explains when to supply output_formats and business_management_no. It never states when-not to use this tool or when the detail sibling is the better choice, which keeps it short of a 5.

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