Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

고용24 기업지원금 신청 필요입력 안내

work24__subsidy__application__requirements
Read-only

REQUIRES prior work24__auth__npki_session__login call with same account_link_id. List what the applicant must supply before any write: institution-provided values, customer-required fields, registered payment accounts, and how attachments are procured (the document list itself is issued by draft_validate, keyed by 접수번호). Read-only — call this before workplace_save. 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
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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces it while adding non-annotation context: the login prerequisite, the per-call token cost ('호출마다 토큰 1소진'), and the fact that the returned document list is issued elsewhere. The idempotency paragraph is disclosed but never explains why a read-only lookup needs a recovery key, which is the one loose end.

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?

Purpose and prerequisites are correctly front-loaded in the first two sentences, but the five-sentence idempotency block dominates the middle of a read-only tool description and repeats guidance that mainly matters for the write siblings. The 'anonymous taste calls' phrasing is an unexplained typo that costs a clause of clarity.

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 1 required parameter and no output schema, the description covers prerequisite, scope, sibling boundary, and cost — enough to invoke correctly. Only the return shape is left implicit, which is acceptable since it is a read-only enumeration tool whose value is self-evident from the purpose statement.

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; the description earns above that by binding the session prerequisite to a named parameter ('same account_link_id') and by carrying the full request_idempotency_key semantics that the schema defers to ('see the tool description'). It distinguishes request_idempotency_key from a provider-side idempotency_key field, which the schema does not.

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 what the applicant must supply before any write') and enumerates the four content categories returned. It explicitly carves out the boundary against draft_validate, which owns the document list, so an agent can separate the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit precondition ('REQUIRES prior work24__auth__npki_session__login call with same account_link_id') and an explicit placement in the workflow ('call this before workplace_save'). It also names the sibling whose output this tool does not return, which is exactly the routing information an agent needs.

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