Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

위택스 공동인증서 로그인

wetax__session__login

Call this FIRST before any other wetax tool. 콘솔에 등록한 사업장 공동인증서로 위택스에 로그인해, 이후 신고 단계와 조회가 함께 쓰는 세션을 만듭니다. 인증서 비밀번호나 인증서 파일은 호출 값으로 받지 않습니다. 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.

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. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already say it is not read-only and not destructive; the description adds that it creates a shared session, accepts no certificate password/file as call values, consumes one token per call, and should be called again after expiry. The idempotency-key paragraph adds retry semantics, though it does not describe failure modes or session lifetime.

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 first-call instruction is front-loaded, but the description mixes English and Korean and spends several sentences on boilerplate idempotency rules, including the confusing 'anonymous taste calls' phrasing. It is usable but not as tight as it could be.

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 an authentication tool with two optional parameters and no output schema, the description covers the key context an agent needs: ordering, session reuse, credential handling, re-login, and token cost. Only error behavior and session lifetime are left implicit.

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 account_link_id is already documented. The description supplements request_idempotency_key with generate/save/reuse/new-key semantics and notes that certificate secrets are not call parameters, adding real meaning beyond the schema.

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: it logs in to Wetax with a workplace joint certificate and creates a session reused by later reporting and inquiry tools. It also distinguishes this as the first call before any other wetax tool, so the agent can tell it apart from the tax query/report siblings.

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?

It gives explicit ordering ('Call this FIRST before any other wetax tool') and a re-call condition when another tool reports an expired session. It does not spell out a when-not case or name other login alternatives, but for this provider login the context is clear.

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