Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

고용24 기업지원금 사전진단 조회

work24__subsidy__diagnosis__search
Read-only

REQUIRES prior work24__auth__npki_session__login call with same account_link_id. Run the work24 (고용24) 사업주 사전진단 for one workplace across the measured subsidy programmes and return a verdict per programme (eligible / ineligible / undetermined - undetermined is never counted as eligible). Read-only. Path A atomic - the same call the subsidy_pack diagnosis leg makes. 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
output_formatsNoOptional. Also return this result as a file (Excel (xlsx)) in artifacts[] of the result. Omit it for data only.
programme_keysNoCatalog programme keys (e.g. w24_b0010). Omit for every programme that has a 사전진단.
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).
application_yearNo신청연도 YYYY. Defaults to the current year.
business_management_noNo11-digit 고용보험 사업장관리번호. Omit to use the one saved at login.
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. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/destructiveHint, and the description confirms 'Read-only' without contradiction. Beyond that it discloses substantive behavior: token cost per call (호출마다 토큰 1소진), xlsx artifact production, 15-minute download_url lifetime, 7-day file retention, and idempotency semantics. Some received boilerplate about anonymous 'taste calls' and recovery receipts is irrelevant to an authenticated-only tool and adds noise rather than clarity.

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 and the verdict semantics are correctly front-loaded, but the middle section sprawls into platform-wide boilerplate about anonymous recovery receipts and taste calls that do not apply here. Several sentences are dense and hard to parse in one pass (the receipt paragraph runs four sentences on a non-applicable case).

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 carries the burden and does cover the important returns: per-programme eligibility verdicts and artifacts[] with download_url and retention windows. What is missing is the response envelope for the verdicts themselves (fields, ordering, or how programme results are keyed) beyond the three-state terminology.

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. The description adds real meaning the schema does not: request_idempotency_key must be generated and saved before the first request, reused only to recover a lost response, and kept distinct from any provider-specific idempotency_key. It also clarifies output_formats is only for file emission and that programme_keys omission means every programme with a 사전진단.

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 — running the 고용24 사업주 사전진단 for one workplace across measured subsidy programmes — and explicitly describes the output shape (a verdict per programme, with undetermined never counted as eligible). It also distinguishes itself from siblings by noting it is 'Path A atomic - the same call the subsidy_pack diagnosis leg makes' rather than an application or catalog browse tool.

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?

Opens with a hard prerequisite ('REQUIRES prior work24__auth__npki_session__login call with same account_link_id') and tells the agent what to do when a result link expires (xdata__job__result with job_id). It does not explicitly contrast with sibling application tools such as application__requirements or application__target_search, so the when-not guidance is thin.

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