XBOSS

보험료 산출내역 조회

si4n__premium_calculation__inquiry

REQUIRES prior si4n__session__login call with same account_link_id. 조회만 합니다. 고지 월 하나의 보험료를 가입자 수, 월 보험료, 고지 보험료, 연체금, 지원금, 소급 보험료로 나눠 돌려줍니다. 보험료가 늘어난 까닭을 찾을 때 씁니다. 개인별 상세와 엑셀 내려받기는 제공하지 않습니다. 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": {
      "insurance_type": "<insurance_type>",
      "notice_year": "<notice_year>",
      "notice_month": "<notice_month>"
    },
    "name": "si4n__premium_calculation__inquiry"
  }
}

Input Schema

Name	Required	Description
`notice_year`	Yes	Notice year, four digits.
`notice_month`	Yes	Notice month.
`insurance_type`	Yes	One insurance, or all for the combined breakdown.
`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/5.0

Behavior5/5

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

Goes well beyond the annotations by explaining why readOnlyHint=false: the call creates an XBOSS task and persists the result, so it is not purely read-only despite being a lookup, and it consumes one token per call. It also spells out idempotency-key lifecycle (new key per execution, reuse only to recover a lost response) and warns that a provider-specific idempotency_key is a different field. This is exactly the side-effect and cost context the structured fields cannot convey.

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?

Prerequisite and purpose are correctly front-loaded, but the text is padded with generic boilerplate that does not apply here ('not available to anonymous taste calls', '기관 데이터 변경은 도구별 실행 내용과 기존 확인 절차를 따릅니다'). It also opens with '조회만 합니다' and later states the call is not purely read-only, forcing the reader to reconcile the two sentences.

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?

With no output schema, the description compensates by enumerating the returned breakdown fields, and it covers auth prerequisite, cost, side effects, and idempotency. The only shortfall is the unaddressed ambiguity between the opening 'inquiry only' framing and the later read-only disclaimer, which could make an agent uncertain about whether the call mutates institution data.

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 documents notice_year, notice_month, insurance_type, account_link_id, and request_idempotency_key. The description adds only relational meaning for account_link_id ('same account_link_id' as the login call) and defers the idempotency key to the schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource (retrieving one notice month's premium breakdown) and enumerates the exact fields returned: subscriber count, monthly premium, billed premium, arrears, subsidy, retroactive premium. It does not name or contrast with the similar-sounding sibling si4n__premium__inquiry, so an agent must infer the boundary from the 'no per-person detail, no Excel download' clause rather than from an explicit differentiation.

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 concrete use case ('use when finding why the premium increased'), a hard prerequisite (prior si4n__session__login with the same account_link_id), and explicit exclusions (no individual-level detail, no Excel export). It stops short of naming an alternative tool to use when those exclusions apply.

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?