Skip to main content
Glama
Sign In

XBOSS

by kr.xdata
OverviewDiscussionsAdmin

4대보험 FAQ 상세 조회

fourinsure__b1__resources__faqs__detail

REQUIRES prior fourinsure__session__login call with same account_link_id. Get FAQ detail. 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": {
      "qstn_sn": "<qstn_sn>"
    },
    "name": "fourinsure__b1__resources__faqs__detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
qstn_snYesFAQ question serial number (질문 일련번호). Obtain from faqs.list.
account_link_idNo연동 ID(UUID v4). 선택 입력입니다. 비워 두면 서버가 API 키로 연동을 찾아 씁니다. 같은 기관에 인증서를 여러 개 연동했을 때만 직접 입력해 주세요. 기관마다 ID 가 다릅니다.
current_page_noNoList page the target row was found on. Optional; defaults to 1.
request_idempotency_keyNoOptional same-request recovery key for authenticated calls; see the tool description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and the description consistently explains why: each call consumes one token, creates an XBOSS task and stores its result regardless of whether the institution original was read. That adds real behavioral context (cost, side effects, mutation implications) the annotations alone don't convey. It still omits failure behavior, e.g. what happens when qstn_sn is unknown.

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 idempotency discussion sprawls over five sentences and a provider-idempotency-key caveat that does not apply to any parameter in this schema. The trailing Korean boilerplate about institution data changes is templated and not specific to this read-oriented FAQ call.

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?

For a low-complexity tool with fully documented parameters, the prerequisites, token cost and idempotency rules are covered. What is missing is any indication of the returned FAQ payload (no output schema exists) and error conditions, so an agent knows how to call it but not what it will get back.

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 semantics the schema does not: when to reuse request_idempotency_key for lost-response recovery versus issuing a new key, and that a provider-specific idempotency_key is a distinct field. The account_link_id and current_page_no meanings are left entirely to the schema.

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?

"Get FAQ detail" names a specific verb and resource, and the qstn_sn parameter ties it to a single FAQ record, so it is distinguishable from faqs__list by name and title. It stops short of explicitly naming the list sibling or what the detail record contains.

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

Usage Guidelines3/5

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

It gives a hard prerequisite (prior fourinsure__session__login with the same account_link_id) and idempotency-key protocol, which is genuine usage context. However, there is no explicit when-to-use/when-not-to-use versus faqs__list or other detail siblings, so alternatives are left to inference.

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