XBOSS

4대보험 FAQ 목록 초기화

fourinsure__b1__resources__faqs__list_init

No credential or login required. Initialize FAQ list for 4대보험. 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fourinsure__b1__resources__faqs__list_init"
  }
}

Input Schema

Name	Required	Description	Default
`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

B3.2/5.0

Behavior4/5

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

Beyond the annotations it discloses several non-obvious traits: each call consumes one token, the request creates an XBOSS job and persists its result, and the call is explicitly not purely read-only, which aligns with and enriches readOnlyHint=false. It also states no login is needed and explains the idempotency-key lifecycle in detail. Only missing pieces are error behavior and rate-limit specifics.

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 no-credential and purpose statements are front-loaded, but the body mixes Korean and English, repeats the new-request/no-key idea twice, and spends most of its length on an optional parameter's idempotency semantics. The phrase 'anonymous taste calls' is unclear and reads as a translation artifact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Behavioral context (token cost, job creation, non-read-only nature) is well covered for a session-initialization tool, but the description never explains what initialized state it produces or how the subsequent faqs__list/faqs__detail calls depend on it. With no output schema, that gap matters for correct sequencing.

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, but the description adds genuine meaning: reuse the key only to recover the same request after a lost response, use a new key for a new execution, omit it and the call becomes a new request, the key is unavailable to anonymous calls, and it must not be confused with a provider-specific idempotency_key. That is substantive semantics beyond the one-line schema description.

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

Purpose3/5

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

The description names the resource (FAQ list for 4대보험) and a verb ('Initialize'), but 'initialize' is never explained and the sibling 'faqs__list' is never mentioned, so an agent cannot tell what an init call actually returns versus a list call. The purpose is recognizable but vague at the decision point.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states that no credential or login is required, which is useful context, but gives no guidance on when to call this versus fourinsure__b1__resources__faqs__list or faqs__detail, nor any sequencing or prerequisite rules. The only conditional guidance concerns the idempotency key, not tool selection.

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?