Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

고용24 기업지원금 대상자 후보 조회

work24__subsidy__application__target_search

REQUIRES prior work24__auth__npki_session__login call with same account_link_id. List the 사업장 고용보험 피보험자 who can be named as subsidy targets. Targets are chosen from this list, never created, so no resident registration number is required from the caller. Nothing is submitted. Some programmes save the draft between screens; safety.save_executed in the result says whether that happened. 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
pageNo1-based 페이지 (기본 1)
queryNo대상자 성명 부분검색. 비우면 피보험자 전체.
page_sizeNo페이지 크기 (기본 10)
receipt_noYes민원신청접수번호 (cvplRqutRcno). workplace_save 가 발급한 값.
programme_keyYes카탈로그 사업 키 (예: w24_b0010 고용촉진장려금). subsidy_pack 진단 결과의 programme_key 를 그대로 넣는다.
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. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: no PII (resident registration number) is required, nothing is submitted, some programmes persist a draft between screens with the outcome exposed as safety.save_executed, and each call consumes one token (호출마다 토큰 1소진). This also explains why readOnlyHint is false despite being a listing tool.

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

Conciseness4/5

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

The prerequisite is correctly front-loaded and each sentence carries information, but the idempotency paragraph runs four sentences and the 'nothing is submitted' claim sits slightly awkwardly next to the draft-save disclosure, costing a bit of crispness.

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 one behavioral return signal (safety.save_executed) and pagination/filter params are covered by the schema. It stops short of describing the shape of returned candidate records, which an agent might want before chaining into target_save.

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 adds real meaning for request_idempotency_key (generate before first call, reuse only for lost-response recovery, ignored for anonymous calls) and reinforces the account_link_id matching requirement.

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 (List) and resource (사업장 고용보험 피보험자 candidates for subsidy targets), and clarifies the tool only retrieves candidates while targets are 'chosen from this list, never created', which distinguishes it from the sibling target_init/target_save tools.

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 a hard prerequisite (prior work24__auth__npki_session__login with the same account_link_id) and explains the search-vs-create relationship with the save/init siblings. It does not name a specific alternative for narrower/broader queries (e.g. diagnosis search), so it falls short of explicit when-not guidance.

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