XBOSS

고용24 로그인

work24__auth__npki_session__login

Call this FIRST before any other tool for this provider. 공동인증서(법인)로 고용24 에 로그인합니다. 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소진 요청 처리 시 XBOSS 작업을 생성하고 처리 결과를 저장합니다. 기관 원본의 조회 여부와 별개로 이 호출은 순수 읽기 전용이 아닙니다. 기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "business_registration_no": "<business_registration_no>"
    },
    "name": "work24__auth__npki_session__login"
  }
}

Input Schema

Name	Required	Description
`isoa_no`	No	사무대행기관 번호입니다. 회원 유형이 BE902 일 때만 필요합니다.
`account_link_id`	No	연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
`member_type_code`	No	회원 유형입니다. BE904 는 일반사업자(기본값), BE902 는 사무대행기관입니다.
`business_management_no`	No	11자리 고용보험 사업장관리번호입니다. 장려금 신청 화면에서 필요합니다.
`request_idempotency_key`	No	Optional same-request recovery key for authenticated calls; see the tool description.
`business_registration_no`	Yes	10-digit business registration number (e.g. 1234567890)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, and the description reinforces this correctly by stating the call is not purely read-only and creates an XBOSS task whose result is stored. It also discloses a per-call cost (토큰 1소진) and detailed idempotency-key recovery semantics — real value beyond the annotations. The closing line about 기관 데이터 변경 following per-tool procedures is vague boilerplate.

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 critical ordering instruction is correctly front-loaded, but the body mixes Korean and English, repeats idempotency rules at length, and ends with generic text about institutional data changes that does not help the caller. Several sentences could be trimmed without losing meaning.

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?

For a login tool with 100% schema coverage and no output schema, the description covers ordering, cost, side effects, and idempotency. It does not state what credentials or certificate material must already be available, nor what a caller should do after a failed login, leaving a modest gap for an authentication entry point.

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, but the schema's request_idempotency_key description explicitly defers to the tool description, and the description fills that gap with reuse rules and the note that anonymous calls cannot supply it. It also clarifies that a provider-specific idempotency_key is a different field, preventing a likely confusion.

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

Purpose4/5

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

States a specific verb and resource: logs in to 고용24 using a corporate 공동인증서 (joint certificate). The 'for this provider' phrasing scopes it away from the comwel/nps_edi npki_session__login siblings, though it never names an alternative explicitly. An agent can identify the action without opening the schema.

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?

'Call this FIRST before any other tool for this provider' gives explicit ordering guidance, which is the key usage question for a login tool. It lacks any when-not guidance or a pointer to work24__auth__session__status for checking an existing session, so the agent must infer whether re-login is safe.

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

All XBOSS tools Inspect

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

Need Help?