Skip to main content
Glama

고용24 기업지원금 신청 이력 조회

work24__subsidy__application__history

REQUIRES prior work24__auth__npki_session__login call with same account_link_id. 조회만 합니다. 이 사업의 지난 고용24 지원금 신청과 처리 상태(작성중, 처리중, 보완요청, 반려, 처리완료 등)를 돌려줍니다. 상태의 기준은 고용24 입니다. 아직 지원하지 않는 사업은 WORK24_SUBSIDY_APPLICATION_HISTORY_NOT_MEASURED 오류로 끝나며, 고용24 화면의 어디에서 확인하는지 알려 줍니다. Files: a document generated from this result, as Excel (xlsx) only when requested in output_formats, listed in artifacts[] of the result with a download_url that works for 15 minutes; each file is kept for 7 days. If a link has expired, call xdata__job__result with the job_id from the result for fresh links. For an anonymous result, keep its private recovery_receipt and send it with the original job_id or pack_run_id to xdata__job__result. It grants access to that result only, until the original file retention expires. Do not publish it. Losing it cannot be repaired by signing up. The receipt also works if the client later signs in; it does not grant access to other results. Without a receipt, results require the original account and lane. 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": {
      "programme_key": "<programme_key>"
    },
    "name": "work24__subsidy__application__history"
  }
}

Input Schema

NameRequiredDescriptionDefault
date_toNo조회 종료일(YYYYMMDD). date_from 과 함께 입력하거나 둘 다 비웁니다.
date_fromNo조회 시작일(YYYYMMDD). date_to 와 함께 입력하거나 둘 다 비웁니다. 둘 다 비우면 오늘(한국 시간)까지 최근 30일을 조회합니다.
programme_keyYes카탈로그 사업 키 (예: w24_b0010 고용촉진장려금). subsidy_pack 진단 결과의 programme_key 를 그대로 넣는다.
output_formatsNo선택 입력입니다. 결과를 엑셀(xlsx) 파일로도 받으려면 입력해 주세요. 파일은 결과의 artifacts[] 에 실립니다. 비워 두면 데이터만 받습니다.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
business_management_noNo11-digit 고용보험 사업장관리번호. 비우면 로그인 시 저장된 값을 쓴다.
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Goes well beyond the annotations: each call consumes one token, a XBOSS job is created and the result stored, and the call is explicitly declared not purely read-only despite being an inquiry. It also discloses the 15-minute download_url lifetime, 7-day file retention, the NOT_MEASURED error, and idempotency-key reuse rules. Much of the file/receipt material is generic platform boilerplate, which dilutes rather than contradicts the disclosure.

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 and the purpose plus status list are clear, but the definition is bloated with generic paragraphs about artifacts, recovery_receipt handling, and idempotency semantics that repeat platform-wide rules. For an authenticated-oriented inquiry tool, the anonymous-receipt passage in particular does not earn its space.

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?

Covers what an agent needs: auth prerequisite, scope and status vocabulary, unsupported-programme error, optional Excel artifact and its retention, per-call cost, and idempotency behavior. With no output schema, it also sketches the return shape (artifacts[], statuses) reasonably well, leaving only field-level detail unstated.

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 description coverage is 100%, so the schema already explains date_from/date_to pairing and the 30-day default, programme_key catalog keys, output_formats, business_management_no fallback, and the idempotency key. The description adds no parameter-level meaning beyond that, 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?

States a specific verb and resource: returns this programme's past 고용24 subsidy applications and their processing statuses (작성중, 처리중, 보완요청, 반려, 처리완료). An agent can tell it is a history/status lookup rather than a submit or modify action, though no sibling is named explicitly.

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 a hard prerequisite (prior work24__auth__npki_session__login with the same account_link_id) and an explicit failure mode with a boundary: programmes not yet supported end in WORK24_SUBSIDY_APPLICATION_HISTORY_NOT_MEASURED. It stops short of naming which sibling to call instead for other application operations.

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