Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

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

work24__subsidy__application__history
Read-only

REQUIRES prior work24__auth__npki_session__login call with same account_link_id. List past work24 subsidy applications for this programme with their processing state (작성중/처리중/보완요청/반려/처리완료/…). Read-only - the state of record is work24, not XBOSS. Not every programme is supported yet; for one that is not, the call fails with WORK24_SUBSIDY_APPLICATION_HISTORY_NOT_MEASURED and says where to check on the work24 screen. 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소진

Input Schema

NameRequiredDescriptionDefault
date_toNo조회 종료일 YYYYMMDD. 비우면 오늘.
date_fromNo조회 시작일 YYYYMMDD. 비우면 date_to 기준 30일 전(화면 기본값과 동일).
programme_keyYes카탈로그 사업 키 (예: w24_b0010 고용촉진장려금). subsidy_pack 진단 결과의 programme_key 를 그대로 넣는다.
output_formatsNoOptional. Also return this result as a file (Excel (xlsx)) in artifacts[] of the result. Omit it for data only.
account_link_idNoAccount link ID (UUID v4). Optional — the server auto-resolves from your API key when omitted. Provide explicitly only when you have multiple certificates for the same provider. Each institution has a separate ID (Hometax != NHIS != NPS != FourInsure).
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. Changed1 schema field changed
    • addedInput schema / properties / request_idempotency_key
      Added value: +{
+  "description": "Optional same-request recovery key for authenticated calls; see the tool description.",
+  "maxLength": 128,
+  "minLength": 1,
+  "pattern": "^[\\x20-\\x7E]+$",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / output_formats
      Added value: +{
+  "description": "Optional. Also return this result as a file (Excel (xlsx)) in artifacts[] of the result. Omit it for data only.",
+  "items": {
+    "enum": [
+      "xlsx"
+    ],
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array",
+  "uniqueItems": true
+}
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds real context beyond them: work24 is the state of record (not XBOSS), the specific unsupported-programme error code, xlsx artifacts with a 15-minute download_url and 7-day retention, and the token cost per call ('호출마다 토큰 1소진'). Some of the receipt/idempotency prose reads as boilerplate shared across tools rather than history-specific behavior.

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, but the body degenerates into a long run-on paragraph mixing artifact retention, anonymous recovery_receipt policy, and idempotency-key rules that are largely generic to the platform. The content that is specific to this tool — states, unsupported-programme error, source of record — is buried in that block.

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?

With no output schema, the description does supply the returned states and the artifact channel (artifacts[] with download_url), plus the recovery path via xdata__job__result for expired links. For a one-required-parameter read tool this is close to sufficient, though it never sketches the record structure beyond the state field.

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; however the description carries semantics the schema explicitly defers to it ('see the tool description') by explaining request_idempotency_key reuse rules — reuse only to recover a lost response, new key for a new execution. Date defaults and account_link_id resolution are already fully documented in the schema and add nothing here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: list past work24 subsidy applications for a given programme, including their processing state, and enumerates the state values (작성중/처리중/보완요청/반려/처리완료). It is clearly distinguishable from write-oriented siblings like work24__subsidy__application__submit, __modify, or __target_search.

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?

Front-loads the prerequisite ('REQUIRES prior work24__auth__npki_session__login call with same account_link_id') and gives an explicit exclusion with a named failure mode: unsupported programmes fail with WORK24_SUBSIDY_APPLICATION_HISTORY_NOT_MEASURED and a pointer to the work24 screen. It does not, however, contrast itself with nearby read siblings such as work24__subsidy__diagnosis__search or __target_search.

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

All XBOSS toolsInspect
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