Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

고용24 로그인

work24__auth__npki_session__login

Call this FIRST before any other tool for this provider. Login to work24 (고용24) via 공동인증서 (corporate joint certificate). 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
isoa_noNo사무대행기관 번호입니다. 회원 유형이 BE902 일 때만 필요합니다.
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).
member_type_codeNo회원 유형입니다. BE904 는 일반사업자(기본값), BE902 는 사무대행기관입니다.
business_management_noNo11자리 고용보험 사업장관리번호입니다. 장려금 신청 화면에서 필요합니다.
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.
business_registration_noYes10-digit business registration number (e.g. 1234567890)

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. Changed3 schema fields changed
    • changedInput schema / properties / business_management_no / description
      Previous value: -"11-digit 고용보험 사업장관리번호. Required for 장려금 신청 screens."New value: +"11자리 고용보험 사업장관리번호입니다. 장려금 신청 화면에서 필요합니다."
    • changedInput schema / properties / isoa_no / description
      Previous value: -"사무대행기관 번호. Required only when member_type_code=BE902."New value: +"사무대행기관 번호입니다. 회원 유형이 BE902 일 때만 필요합니다."
    • changedInput schema / properties / member_type_code / description
      Previous value: -"회원유형: BE904 일반사업자 (default) or BE902 사무대행기관"New value: +"회원 유형입니다. BE904 는 일반사업자(기본값), BE902 는 사무대행기관입니다."
  3. First observed

TDQS

A5/5.0
Behavior5/5

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

The description adds critical behavioral traits beyond the annotations, including the operational cost (1 token cost per call) and the complex rules surrounding the idempotency key (required vs. optional, reuse constraints). This level of detail makes the tool highly predictable.

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

Conciseness5/5

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

Although dense, every sentence is critical instructional data for this specific API flow. It is highly front-loaded with the most important operational constraints and sequence requirements.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that this is a stateful authentication tool with complex requirements (idempotency, required initial call), the description is exceptionally complete. It addresses operational flow, token costs, and multi-call management which are not covered by the input/output structure alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

While the schema provides details, the description adds vital context for the `request_idempotency_key`. It explains that the key is crucial for recovering lost requests, which is far more informative than the schema's brief placeholder reference. This high context compensates for the schema completeness.

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?

The purpose is clearly stated: login to work24 using the corporate joint certificate. It is distinct from other session/login tools via the specific provider prefix and the description of the required authentication method (공동인증서).

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?

The description provides highly explicit usage rules, stating that this tool must be called 'FIRST before any other tool for this provider.' It also dictates the lifecycle of the request_idempotency_key, offering clear instructions on when to generate, reuse, and avoid using it.

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