XBOSS

사회보험통합징수포털 로그인

si4n__session__login

Call this FIRST before any other tool for this provider. 사업장 인증서로 로그인하고 다른 사회보험통합징수포털 도구들이 함께 쓰는 세션을 저장합니다. 도구가 세션이 만료됐다고 알리면 다시 호출합니다. 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": "si4n__session__login"
  }
}

Input Schema

Name	Required	Description
`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.
`business_registration_no`	Yes	사업자등록번호 - 숫자 열 자리(하이픈 없이). 예: 1234567890.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare readOnlyHint=false/destructive=false/openWorld=false; the description adds cost and side-effect detail the annotations cannot express, notably 토큰 1소진 per call, XBOSS 작업 생성 and result persistence, session storage shared with sibling tools, and the explicit note that the call is not purely read-only despite query-like framing.

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 opening two lines are correctly front-loaded and high value, but the middle idempotency block is long, partly redundant ("Without it, calling again remains a new request") and the phrase "anonymous taste calls" is unclear in this context. It mixes provider guidance with generic cross-cutting boilerplate, diluting an otherwise tight definition.

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 3-parameter session establishment tool with annotations and no output schema, the description covers prerequisites, session reuse, cost, and idempotency adequately. What is missing is failure behavior — no mention of what an agent should do if certificate authentication or account_link_id resolution fails.

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 already 100%, so the baseline is 3; the description earns above that by explaining the lifecycle of request_idempotency_key — generate before the first request, reuse only to recover a lost response, use a fresh key for a new execution, and keep any provider-specific idempotency_key separate. The account_link_id and business_registration_no semantics are mostly left to the schema, which handles them well.

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 — logging in with a business certificate to the 사회보험통합징수포털 and persisting the resulting session that sibling tools share. It also explicitly scopes itself relative to the many sibling session__login tools by naming its provider, so an agent can pick the right one 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 Guidelines5/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" plus the re-call condition ("도구가 세션이 만료됐다고 알리면 다시 호출합니다") gives explicit when-to-use and when-to-repeat guidance. The ordering constraint and expiry trigger leave nothing to inference.

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?