Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

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

si4n__session__login

Call this FIRST before any other tool for this provider. Signs in with the workplace certificate and stores the session the other si4n tools reuse. Call it first; call it again if a tool reports the session expired. 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
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).
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.
business_registration_noYes사업자등록번호 - 숫자 열 자리(하이픈 없이). 예: 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. Changed2 schema fields changed
    • addedInput schema / properties / business_registration_no
      Added value: +{
+  "description": "사업자등록번호 - 숫자 열 자리(하이픈 없이). 예: 1234567890.",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "business_registration_no"
+]
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses that the session is stored and reused by other si4n tools, that re-login is required after expiration, and that each call consumes one token ('호출마다 토큰 1소진'). It also explains idempotency-key behavior for recovering a lost response, which is meaningful operational context.

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 'call this FIRST' instruction is front-loaded, but the description is repetitive ('Call this FIRST' then 'Call it first') and includes idempotency boilerplate that is longer than necessary for a login tool. The trailing Korean token note and the unclear 'anonymous taste calls' phrase reduce polish.

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, it covers the essential first-call rule, session reuse, re-login trigger, token cost, and idempotency semantics. It does not describe what a login failure looks like or detail the certificate prerequisites beyond 'workplace certificate', leaving minor gaps.

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 the baseline is 3. The description adds substantial meaning for request_idempotency_key beyond the schema's deferral, explaining when to generate it, when to reuse it after a lost response, when to use a new key, and that provider-specific idempotency_key is a different field.

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 description states a specific verb and resource: signs in with the workplace certificate and stores the session for reuse by other si4n tools. The phrase 'for this provider' distinguishes it from the many other session/login sibling tools for other providers.

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?

It explicitly says to call this FIRST before any other tool for this provider and to call it again if a tool reports the session expired. That gives a clear when-to-use rule with a concrete re-invocation trigger.

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