XBOSS

정부24 로그인

gov24__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

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": "gov24__session__login"
  }
}

Input Schema

Name	Required	Description	Default
`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.2/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=false/openWorldHint=false/destructiveHint=false; the description goes well beyond by disclosing token cost per call ("호출마다 토큰 1소진"), that a request creates a XBOSS job and stores the result, and that the call is explicitly not purely read-only — directly consistent with readOnlyHint=false. It stops short of session lifetime or what credentials/state the session holds, so it is not fully complete.

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 lead sentence is correctly front-loaded, but the body is a mixed Korean/English block where generic idempotency boilerplate and the XBOSS/token note interleave with the login-specific instruction. Several clauses ("anonymous taste calls", the provider-specific idempotency caveat) read as templated filler for a login tool, costing parseability.

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 no output schema, the description covers ordering, expiry re-auth, cost, and idempotency recovery. The main omissions are what the persisted session returns and how long it lasts, but the account_link_id schema text covers the multi-certificate case.

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% and account_link_id is already well documented in-schema. The description still adds real semantics for request_idempotency_key: reuse the same key only to recover a lost response, use a new key for a new execution, and keep provider-specific idempotency_key separate — more than the schema's pointer provides.

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+resource (로그인 / 세션 저장) and pins its position in the workflow: "Call this FIRST before any other tool for this provider." It also ties the session to the gov24 certificate-issuance tools, which is exactly the sibling relationship an agent needs to resolve.

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 when-to-use (before any other tool for this provider) and a re-invocation trigger ("도구가 세션이 만료됐다고 알리면 다시 호출합니다"). No explicit when-not or named alternative is offered, but among the sibling `*__session__login` tools the provider scoping makes the choice unambiguous.

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?