XBOSS

4대보험 EDI 로그인

fourinsure__session__login

Call this FIRST before any other tool for this provider. Login to FourInsure (4대보험) EDI. Returns API_KEY. 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fourinsure__session__login"
  }
}

Input Schema

Name	Required	Description
`auth_provider`	No	Auth provider: manual_session \| npki_anysign (default: npki_anysign)
`account_link_id`	No	연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
`request_idempotency_key`	No	Optional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, and the description usefully adds that each call consumes one token (토큰 1소진), creates an XBOSS task with a stored result, and is explicitly not pure read-only — consistent with the annotations and genuinely additive. However, the trailing Korean boilerplate about provider data changes is generic and defers specifics elsewhere instead of disclosing concrete effects for this tool.

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 directive is front-loaded, but the middle is padded: idempotency guidance is restated in several sentences and the closing Korean block (token consumption, XBOSS task, provider-record caveat, generic change-control sentence) reads as boilerplate rather than tool-specific information.

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 three-parameter, zero-required login tool with no output schema, the description covers the essentials: call ordering, the API_KEY return, per-call cost, non-read-only side effects, and idempotency handling. Only failure/retry-after-auth-error behavior is left unstated.

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 auth_provider and account_link_id are already well documented. The description still adds real semantics for request_idempotency_key — generate before the first request, reuse only to recover a lost response, new key per new execution, without it a repeat call is a new request, and do not conflate it with a provider-specific idempotency_key.

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 ('Login to FourInsure (4대보험) EDI') and names the concrete return value ('Returns API_KEY'). The provider name plus the 'FIRST before any other tool for this provider' framing separates it cleanly from the many sibling provider logins (nhis_edi, nps_edi, hometax, etc.).

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?

Gives explicit ordering guidance ('Call this FIRST before any other tool for this provider'), which is the key decision an agent must make with ~25 sibling tools. It does not cover what to do on login failure or when to prefer a session-status/id-password alternative, so it stops short of full when/when-not coverage.

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?