Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

4대보험 공통코드 목록

fourinsure__b1__common__com_cd__list
Read-only

REQUIRES prior fourinsure__session__login call with same account_link_id. 자격취득·상실 신고서의 사유·직종 칸에 넣는 공통코드(코드 값과 이름)를 분류 아이디별로 조회합니다(예: B112, D114, A101). 조회만 하며 기관에 저장하거나 제출하지 않습니다. 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
com_cd_clsf_idYesCode classification id, e.g. B112, D114, A101.
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/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this ('조회만 하며 기관에 저장하거나 제출하지 않습니다'). It adds non-obvious operational context the annotations do not cover: one token is consumed per call and there is an idempotency-key recovery protocol. However, the idempotency paragraph is generic boilerplate that reads oddly for a pure read-only list call, which slightly muddies rather than sharpens the behavioral picture.

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 prerequisite is correctly front-loaded, but the multi-sentence idempotency-key block is disproportionate boilerplate for a read-only lookup and dilutes an otherwise tight Korean purpose statement. The final token-cost note is short and earns its place.

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 read-only lookup with no output schema and full parameter coverage, the description supplies what matters: prerequisites, what is returned (code value plus name), that nothing is persisted, and the call cost. Only the shape of the returned list is left implicit, which is acceptable here.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already defines all three parameters including the classification-id examples and the account_link_id auto-resolution rule. The description adds only marginal framing (that codes are grouped by classification id) 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?

States a specific verb (조회/retrieve) and resource (공통코드, code values and names) and names the concrete downstream use — the reason/occupation fields of acquisition/loss reports — with example classification ids (B112, D114, A101). No sibling tool performs this lookup, so the agent can identify it unambiguously.

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 a clear prerequisite (a prior fourinsure__session__login with the same account_link_id) and a clear context of use. There is no competing alternative tool to route away from, so the absence of explicit when-not guidance is minor.

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